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

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Low Engagement
    • Component/s: Issue - Backend
    • None

      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?

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

              Created:
              Updated:
              Resolved: