-
Suggestion
-
Resolution: Won't Do
-
None
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? 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 related to
-
- Closed
- relates to
-
- Closed
- mentioned in
-
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page")
Page
Failed to load
[JRACLOUD-31260] Bulk move issues will ignore the issue key sequence in the source project
Michael Gysel
added a comment - When moving issues to a new project without any issues it would be nice if JIRA would retain not only the order but also the issue numbers (including any gaps in the sequence.)
This requirement is kind of a prerequisite for the "new-project-and-bulk-move" workaround for JRA-2703.
Michael Gysel
added a comment - When moving issues to a new project without any issues it would be nice if JIRA would retain not only the order but also the issue numbers (including any gaps in the sequence.)
This requirement is kind of a prerequisite for the "new-project-and-bulk-move" workaround for JRA-2703 . 
Pablo Beck
added a comment - I had this same experience recently moving bulk-issues-the worst part is that the old key reference didn't take me to the correct issue-it took me to a whole different issue all together. So the random effect causes some problems beyond random issue key generation.
Pablo Beck
added a comment - I had this same experience recently moving bulk-issues- the worst part is that the old key reference didn't take me to the correct issue -it took me to a whole different issue all together. So the random effect causes some problems beyond random issue key generation.
Thanks for taking the time to raise this issue.
Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts. In part, that means concentrating on those issues that resonate the most with our users.
I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue.
Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me.
Kind Regards,
Kerrod Williams
JIRA Product Management
kerrod.williams at atlassian dot com