-
Suggestion
-
Resolution: Won't Do
-
Jira professional standalone 3.10.2 on Linux (RHEL, 2.6.9-55.0.6.ELsmp) Java: 1.5.0_12-b04
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? 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.
- is related to
-
JRASERVER-13659 Moving an issue back to a previous project SHOULD re-use the 'old' issue key
- Closed
-
JRASERVER-72760 Moving an issue back to a previous project SHOULD re-use the 'old' issue key
- Gathering Interest
- relates to
-
JRACLOUD-78885 Moving an issue back to a previous project SHOULD re-use the 'old' issue key
- Gathering Interest