Problem: When moving an issue from one project to another, the ID changes.
Expected system behavior: to ease traceability, the ID would remain the same after moving.
Comments: I need to know where we stand in May 2017 in terms of having access to a unique issue ID. It was first reported in 2003 and 2004 and I assume that it has been corrected since then because this is major.
Unfortunately, this is not possible apparently. The project key purpose is to tell which project the issue belongs to. Reference here: https://community.atlassian.com/t5/JIRA-questions/Move-issue-between-SD-and-non-SD-project-maintain-Issue-Key/qaq-p/454487
The *ID* actually doesn't change, but you will change the *Key* when an issue moves because the *key* must match the parent project.
You may consider if the need for movement across projects indicates that Components should be used instead, or if you feel the need to move tickets across projects is legit, but want to search you can always search by any of the historical keys, and JIRA will still find it, and never reuse a previously used key.
But still searchable.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
You might have noticed something new on Marketplace in the last several months which was the addition of our new collection pages. We heard feedback that it can be hard to browse apps in Marketplace ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs