-
Suggestion
-
Resolution: Low Engagement
-
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?
- is related to
-
JRACLOUD-73468 Ability to reset the issuekey counter of a Project from the UI
- Closed