How can I define Issue ID and Parent ID before CSV import procedure?

This question is in reference to Atlassian Documentation: Importing data from CSV

How can I define Issue ID and Parent ID before CSV import procedure to avoid cases with duplicating of issues? 


I mean case when you are trying to upload issue with Issue Id which already exists in JIRA.


Thank you.

1 answer

1 accepted

1 votes

You don't. If you already have a existing key,  the import has to assume you are updating existing data,  not creating a duplicate. 

Are Issue ID and Parent ID used only for issues import from CSV?

When I tried to upload same CSV file with one Task and three sub-tasks in it two times in the row I found that second import process has created sub-tasks in already existed(imported in first try) Task.

No, sorry, I think you're misunderstanding what the importer will do.

Let's say that the important fields in here are

  • Issue-ID - representing a JIRA issue id
  • Parent-ID - again, a JIRA issue id, but one that is intended to be the parent
  • Data - some other field with data in it.

If a record has no issue-id or parent-id, the importer has no information about existing data, so it will try to create a new record

If a record has an issue-id, then the importer will check to see if it can find that ID in the target system.  If it can, then the data must be an update of fields.  If it can not, then it has no information and has to assume this is a new issue

If a record has a parent-id, then the system will do the same as above, but working on the assumption that the data is for a sub-task instead

Thank you, Nic.


So if I would like to import several tasks with sub-tasks inside and I would like to avoid case when existed data will be updated because of existed Issue Id will be defined in CSV file. How can I proceed with this? I have to enter Issue ID and Parent ID to CSV file for link between sub-tasks and parent tasks. But I don't know whether entered Issue ID is unique.


Thank you.

Right, that's covered in the docs - go to and read the section "Creating sub-tasks"

I've already read that topic.


Thank you for your help, Nic.

Probably I am not accurate with my questions.


I am trying to import new Task(with sub-tasks) from CSV to existed JIRA Project.

  1. Don't want already existed issues be updated because of my import;
  2. Don't want to lose any other existed data because of my import.

So what Issue ID and Parent ID should I enter to CSV file?

Can I verify somehow which Issue ID and Parent ID are already used?


Thank you.

They can't be "already used", they're part of your data that you set up to show the importer the relationship between "issue on line 87 is a subtask of the issue in line 4"

Thank you, Nic.

Now it is clear for me.

Have a good time.

Suggest an answer

Log in or Join to answer
Community showcase
Teodora [Botron]
Published Thursday in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

377 views 1 13
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot