I am working on the ability to import a CSV file into JIRA. The file contains a set of issues that could be represented with Stories, Epics and Sub-Tasks/Tasks.
My goals are:
1) to create the set of issues into JIRA maintaining the issue types as defined in the CSV file,
2) to keep the relationships between the different issue types contained in the file:
Could you please help me to understand how the file should be configured in order to keep those relationships listed above? Please see how my CSV file looks in order to confirm if this is the expected format:
And this is configuration of file used to map the fields:
In addition, why should I use Tasks instead of Sub-Tasks in order to establish the "parent Story > children Sub-Tasks/Tasks" relationship? I tried with both Task and Sub-Task issue types but the parent-children relationship only worked with Sub-Tasks.
Look forward to any assistance.
Thanks in advance,
First, the difference between Story, Task, and Sub-Task:
Story and Task are both at the standard level of JIRA issue type, while Sub-Task is at the sub-task level. The only issue types that can be sub-tasks to standard issue types are those set up as sub-task issue types. So you can have Story + sub-tasks or Task + sub-tasks, but not Story + tasks under it.
Second, to set up the parent-child relationship, you'll need two additional columns: Issue ID and Parent ID. Issue ID is a sequential numbering of your issues, starting with 1. Parent ID should be filled in on sub-task rows to identify which row's issue will be their parent.
Third, to set up the Epic Link, you'll need two additional columns: Epic Name and Epic Link. Epic Name must be filled in on the epic rows - it's a required field that is usually equivalent to the summary or a shortened version (e.g., Summary "Upgrade Wintel Servers" might have Epic Name "Wintel Upgrade"). The Epic Link field should be filled in on standard issue type rows (i.e., Story or Task) using either the epic's key or the epic's name.
Hope that helps!
In order to get epic links, your method is right, it should work.
To get sub-tasks linked, you need to have 2 more columns: Issue ID and Parent ID. The Issue ID column must contain sequential and unique numbers (1,2,3, etc for example) for all your issues. The Parent ID column will contain values for the subtasks. In that column, each subtask will have the value of the Issue ID of the parent task.
Issue type, Summary, Issue ID, Parent ID
Task, Do something, 1,,
Task, Do something else,2,,
Sub-Task, Do it, 3,1
You will create 2 tasks and a sub-task. The sub tasks will be linked to the "Do something" Task because the value of the parent id column is 1 which corresponds to the first task.
I hope this answers the question.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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