How can I preserve the order of issues when bulk migrating them between Jira projects?

[aromal]

When performing a bulk migration of issues from one Jira project to another, the original order of issues in the Issue Navigator is lost. 

What are the best practices or solutions to ensure that the order of issues remains intact during the migration process?

[John Funk]

Hi Aromal - Welcome to the Atlassian Community!

You can't really control the order on a bulk migration. The only way to ensure that they are in the same order is to migrate them one at a time. 

[aromal]

Hello John,

Migrating one at a time was not possible. Anyway, I compromised the order.

[Mary Jennings]

Hello,

One way to preserve it is by adding a custom field before migration, such as Original Rank or Migration Order, and populating it with sequential numbers reflecting the current order. After migration, you can sort by this field and manually adjust the rank in the new project.

Another option is using Jira Automation to reapply the ranking based on this custom field post-migration. If you're migrating a large number of issues, a script via the Jira REST API could help maintain the order programmatically.

Hope this helps!

[aromal]

Hello Mary,

I wasn’t able to try out this solution. In the end, I had to compromise on the order. Nonetheless, I appreciate your input and hope this helps someone in the future.