Jira issue order during bulk move


During my migration project, one of the tasks I have is splitting 26k issues into separate projects. I need to maintain creation and resolution dates.

I've done some testing, and it looks like creation and resolution dates are maintained -- but the issue id order is not.

For example:

PROJECTA-1 "2003-01-20"

PROJECTA-2 "2004-01-20"

PROJECTA-3 "2005-01-20"

Ends up being:

PROJECTB-1 "2005-01-20"

PROJECTB-2 "2003-01-20"

PROJECTB-3 "2004-01-20"

In other words -- order of input is not respected in output.

This issue occurs in Jira 4.1 -- and also appears to be an issue in Jira 5.24

-- this is a huge annoyance. Anyone have any work arounds?

3 answers

1 accepted

0 votes
Accepted answer

The order I guess is not maintained and I am afraid that it may never be done. See -https://jira.atlassian.com/browse/JRA-15634

Yeah -- I think you are right. Thanks for the link.

0 votes
Timothy Chin Community Champion Jan 27, 2013

What kind of import functionality are you using?

I'm not importing -- I am moving issues within Jira from one project to several new projects. Just an internal bulk move. Which is why I am frustrated -- this seems like functionality that should come out of the box.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,737 views 17 21
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you