Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-13659

Moving an issue back to a previous project SHOULD re-use the 'old' issue key

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      When an issue is moved between projects, the original issue key is left unassigned, it is never reused, and exists solely as a searchable item pointing to the new issue key.
      If the issue is subsequently moved back to the original project it is then assigned a new issue key in the project.
      It would make more sense if the original issue key was reassigned to the issue.

      • Recently we needed to 'undo' an incorrect move, and users subsequently queried why the number had changed.

              Unassigned Unassigned
              8a836f04cd2f Owen Carter
              Votes:
              14 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: