Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

import a list of issues including sub tasks in one import

Hi, I wonder if it is possible to import a new list of jira's and create sub-tasks right away for the jira with yet unknown issue id?

The purpose is to create a tree of Jira's for repeating project jobs.
If we can create an import file we can import this file over and over again to create the same tree for multiple projects.  


thanks in advance and looking forward to responses.


1 answer

1 accepted

1 vote
Answer accepted

Yes, you can, see

I'm not sure the sub-task section is too well written, as a lot of people seem to struggle with it, but this is a less fussy example of a file that will create 5 issues, two tasks and 3 sub-tasks:

  • summary, issue id, parent id
  • story1, 1,,
  • subtask-1-1, 4, 1
  • story2, 8,,
  • subtask-2-1, 16, 8
  • subtask-1-2, 32, 1

Note that the issue id will be imported into "external id" as well, and the "parent id" is not imported directly, because it's only used to make the parent/sub-task link.  Also, you'll need some other columns for issue type etc.  I really did build that file to show you the parent/sub-task structure, nothing else

Hi Nic,
Thank you! Guess this is what I need.
The 'trick' with the parent id linking to the external id (alias of issue id)
I didn't read about that behaviour.

I test this asap.
Thanks again!


Have you been able to make this work? Using the example above I always get an error "Fatal error during import: Parent Issue cannot be null". 

A lot of people have made this work.  Have you tried importing data in the structure given above?  The error you are getting suggests you are trying to create sub-tasks without parent issues.

@Bob - same - anything with the blank value, as the example given of:

  • summary, issue id, parent id
  • story1     , 1          ,,

This line throws the error:


Like Lavern Dowsley likes this

I only get that when the line contains a sub-task type and the parent id is empty

hmm. I tried a lot of different variations.  Any time I had a line that didn't have a value for the parent id, even though it didn't need one, it would fail.  Example of failure:

Summary, issue id, parent id, issue type, epic link

Client Implementation, 21100,,Epic,

Confirm client data, 21101,,Task,21100

Confirm connectivity,21102,21101,Sub-Task,

Odd.  But the next thing to try is completely filling the parent column.  For the parent issues, try a self-reference:

Summary, issue id, parent id, issue type, epic link

Client Implementation, 21100,21100,Epic,

Confirm client data, 21101,21101,Task,21100

Confirm connectivity,21102,21101,Sub-Task,

I am having the same problem. I've tried the self-reference trick but didn't work either. Did Jira change something in their importing process?

I've found the problem. I was using the import CSV option in the filters view that doesn't support this feature. You must use the import CSV Feature in Admin > System > External System Import and choose the CSV option. Everything will work as explained before.

Like # people like this

Using the "Admin" menus....
I'm working on a solution for Project Managers to add a ton of (standard) issues for each project via CSV import.  Having to use the "Admin" menus to import subtasks... that's gonna be a problem for them.

Yeah, the limits on the standard import are a bit of a pain.

However, if this is something that you are doing regularly and a lot, have you considereed automating it instead of doing it via repeated import?   If a computer does something that creates a need for an issue, then instead of write it out into a CSV file for later import, just poke it into Jira directly over the REST API?

i´m using a formula in Excell to create automatic a line with the sub task´s informations.


Excell: =CONCAT("- ";C16;" | ";D16;" / ";"description: ";"""";E16;"""";)






but it´s doing bad when i´m using some fields like "estimated", "component"


How can i solve that?

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Jira Software

Upcoming changes to epic fields in company-managed projects

👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...

14,965 views 38 49
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you