Moved issues to a new project, it did not keep the issues order

[Fernando]

Why is it that when moving issues they do not keep the same order they had in the original project???

I moved all closed issues. The first 7 were marked as tests for control. When moved, they all were assigned issue keys randomly (or at least it looks like a random assignment).

Why is that and how can this be prevented?

I'm sure many users will find this either annoying or problematic. There is no mention in documentation that the order will not be kept when moving issues to a new project.

[Dan Breyen]

Hi Fernando, I looked at Atlassian's JIRA site and found this issue: JRACLOUD-31260 

So it looks like it was brought up but not enough people voted for it at the time.  It's been several years since this was closed.  Maybe it could get created again to see if it can get some more traction for it.  I would expect the order to be kept, or at least give you an option to keep the order. You could ask support at suppport.atlassian.com for some feedback and see if a new issue could be created.

If a new issue does get created, post the number here so people can see it and vote for it.