nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira issue order during bulk move

Bryan Karsh

Hi,

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?

Accepted answers

Renjith Pillai

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

All comments

Timothy

What kind of import functionality are you using?

Bryan Karsh

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.

Renjith Pillai

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

Bryan Karsh

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

issue

jira

sort

bulk-edit

move