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

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

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Low Engagement
    • Issue - Backend
    • None
    • 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.

    Description

      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.
      • Documents that are not on the Jira network need to be updated every time an issue is being moved. Why not save the update when it is not needed?

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              e4d57dd04652 Ohad Gov
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: