You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hello! I am new to Jira and am trying to figure out how to import from an Excel CSV file into Jira to create a new issue with subtasks. I can successfully import the file but it creates stand alone issues. It does not link the issues to a parent issue as subtasks. I have tried starting with a new issue and entering the Issue Key in my spreadsheet. I have tried creating subtasks and entering this Issue Key in the spreadsheet, but no luck.
I have read multiple posts in the Atlassian Community on this but do not understand any of it.
How do I format my Excel spreadsheet? What values should go in the cells so Jira understands to link it to a parent issue and create each line as a subtask?
Thank you in advance!
This document explains what is needed: https://confluence.atlassian.com/jirakb/csv-import-parent-child-mapping-1096095688.html but essentially, you just need to add a column titled 'Parent' and put the parent ticket number in that column.
Thank you! This really helped. I successfully imported from the CSV file into Jira and created my subtasks. To do this, I did end up creating the subtask issues before hand.
Do you know (or can direct me to where I can find the information) if this importing process requires the parent and subtask issue IDs to be mapped? Is it ever possible to not need to create the subtask first but the import process will still link sub-tasks to a parent issue?
Appreciate your help!
You should not need to create the sub-tasks manually. By identifying the project and issue type in your import file the import automation should be able to create the issues without any additional intervention. The only piece you need to add to your base import is to identify the Parent key which will create the parent/child relationship.
Did this not work in your experience?
No, it didn't work. It did create a subtask but it is a stand alone issue (with the Subtask Issue Type) and is not linked to the parent issue.
My spreadsheet columns are pretty basic: Parent ID. Parent Key, Issue Type, Department, Summary, Start Date, Target Date, Description. My success was after adding Issue ID and Issue Key columns with the info for the manually created subtasks.
Were you able to get it to work before adding the Parent ID? I would ensure you can get the import working before adding the Parent, then add the Parent to your import.
Were you able to tell why the import didn't work without the Sub-tasks pre-existing? My best guess is a missing required field!
Yes, I can import to create stand alone issues. Most of my columns will import correctly. I haven't puzzled out yet why Component and Customer Request Type trigger error messages but these are not "critical" fields at this point.
I have been mapping my columns to the fields of the same name. It does give me an error message if I do not have a column mapped to Issue ID. I tested mapping Parent ID to Issue ID and I get an error message, "Unable to link issue from [#] to [#] with link named 'sub-task-link': Cannot find imported issue key for external id '[#]'". I took this to mean that it was looking for the Issue Key for the subtask issue itself. With this error message, no issues are created - not even stand-alone ones.
It looks like Step 4 in the initial link may hold the answer to your question:
For the Task→Subtask relationship to work, copy the 'Issue ID' of the Task issue type and paste it in the 'Parent' column against the Subt-task issue type.