Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-8288

Lost of issue's ID when moving from a project to another one

XMLWordPrintable

    • Icon: Support Request Support Request
    • Resolution: Timed out
    • Icon: Medium Medium
    • None
    • 3.3.2
    • None
    • None

      That's not really a bug, it's a choice, but....

      I was looking for a solution, with JIRA, to put side (not delete) old closed issues. For our compagny, issues don't have to be deleted.
      But, with the passing of years, there's a lot of issues, and the database becomes bigger & bigger.
      Bulk move was a good solution for that, but in moving, the issue change his id (PKEY in database). It's a pity because the users knows their issue with the id... So, we can't use this functionnality.

      Is it a problem for you to keep the old name?

      For example, I have 2 project : A and B.
      I have 3 issues in A : A1, A2,A3

      2 in B : B1, B2

      If I move A3 to B, the issue keeps his name. And the next one in A take A4 for name, the next one in B, B3 or B4 :
      A : A1, A2
      B : B1, B2, A3

      If it's a problem, is it possible to show a column with the real ID in database (which don't change)...

      Thank's for your help.

              Unassigned Unassigned
              bc3d1ae163b7 Anne Diget
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: