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; } } }

Change order of csv-imported subtasks

Kyonho Lee

Hello,

when importing subtasks via the csv import, the subtasks always show up in random order.

Is there a way to have them appear in the same order as in the csv file?

I've tried it without issue IDs for the subtasks.

I've tried with issue IDs in the order of the intended list.

Nothing works.

All Help would be appreciated.

Thanks

~Lee

Accepted answers

All comments

Ramiro P

Hi Lee, as far as I know, you need to have a value Issue ID for the issues that are parents, and a Parent ID for issues that are sub-tasks.

For the Parent issues, the value Parent ID has to be blank and the value Issue ID needs to have a random number different from each other, like a sequence for example.

For the sub-tasks, the value Issue ID has to be blank and the value of Parent ID has to be the same as the Issue ID of the Parent.

While the Parent ID are well mapped with the Issue ID you don't need any order.

You can look here for a better explanation.

Kyonho Lee

I have followed this explanation exactly, with the exception of one attempt with sequential Issue IDs for subtasks.

It's not working.

I'm not sure what you mean by:

While the Parent ID are well mapped with the Issue ID you don't need any order.

I require 17 subtasks per parent and I need them in a specific order.

Thank you.

Ramiro P

Now I understand. You have many sub-tasks per parent, and you want them to be listed in an specific order inside the Parent issue?

Ramiro P

It look like you can't select the order. Have you tried to put inside the CSV file the subtasks upside down? Maybe, but just maybe, the file is read from the top to the bottom and insert each row per turn. Perhaps if you put the Sub-Tasks in a upside down order... It sounds a little delusional

Amichaels

I'm also having this issue. Has anyone found a solution?

TylerA

The recommended solution would be to use the JIRA API to create the issues in a specific sequence. The best way to do this would be to upgrade to JIRA 5 (for the drastically improved REST API) and then have a client (like this python library) parse the CSV and create issues in the exact order necessary.

(Please don't use SOAP. It has bugs like this.)

Kyonho Lee

Thanks for the suggestion, but due to some plugins not supporting JIRA 5 yet upgrading is not an option.

Also we are simple users here. We don't have the resources to build custom solutions.

We were hoping for an out-of-the-box solution for what seems to be an obvious problem with the import of sequential subtasks.

Ramiro P

Hi Lee,

You can check this question about this matter:

https://answers.atlassian.com/questions/55744/preserving-the-order-priority-of-issues-when-importing-csv