-
Suggestion
-
Resolution: Won't Do
-
None
-
None
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
When bulk moving issues from one project to another, the original sequence of the issues issue key will be lost during the process.
As an example, I've created 2 projects (Source Project and Target Project), and created 10 test issues under Source Project:
After bulk moving all 10 issues to the Target Project, the original sequence of the issue key is lost, seems like the new issue key are randomly assigned to those issues:
Hence, it will be great if the original issue key sequence is retained when bulk moving issues, or at least give the user an option to choose the original sequence or not.
- is blocked by
-
JRASERVER-71758 When bulk move issues, add an explicit banner to let the users know that the issues won't be recreated in any particular order
- Gathering Interest
- relates to
-
JRACLOUD-31260 Bulk move issues will ignore the issue key sequence in the source project
- Closed
-
JRASERVER-2703 As an Admin, I want the ability to edit a project's key
- Closed