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

Issue moved back to original project cannot be found using original key when it is moved more than one time

XMLWordPrintable

    • 0
    • 6
    • 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.

      As a user, I want to be able to find an issue by an old key value so that I keep my tracablity.

      Example:
      I have a issue TEST-1. I do a move of this issue to my FOO project, it becomes FOO-1. I then realize that was a mistake and move it back to my TEST project. It is now TEST-2. If I do a quick search or a JQL search for TEST-1 it comes up as not found.

      I have to do a ridiculous amount of searching to try to find this.

      The reason why this is important is that the keys are what are logged in my SCM system. I have situations where the original check in was done under the original key. I now cannot find the tracability of this checkin.

              Unassigned Unassigned
              9e936c6e3422 Mike Winston
              Votes:
              9 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: