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

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

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Unresolved
    • None
    • Issue - Actions
    • Jira professional standalone 3.10.2 on Linux (RHEL, 2.6.9-55.0.6.ELsmp) Java: 1.5.0_12-b04
    • 3
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? 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.

      Attachments

        Issue Links

          is cloned from

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

          • Closed
          relates to

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

          • Closed

          Activity

            People

              Unassigned Unassigned
              e4d57dd04652 Ohad Gov
              Votes:
              8 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated: