/
How to import parent-child related issues?
How to import parent-child related issues?
- Moresimp
- Zsolt Gulyás
- Kojnok Roberta
- Mark Biro (Unlicensed)
Owned by Moresimp
Last updated: Feb 14, 2022 by Zsolt GulyásVersion comment
On this Page
The 2-layer model (task - subtask)
If you would like to create a parent issue with 2 child items like this:
- Story 1
- Sub-task 1.1
- Sub-task 1.2
It is important to know:
- when you paste it into the ImpEx import dialog
- please make sure that you refer to the correct Project name
- always copy the column names too
- Sub-tasks are automatically assigned to the Story that are above them
(More about importing in general: Importing)
Please use this template
| Project | Summary | Issue Type |
|---|---|---|
| Project 1 | Task 1 | Task |
| Project 1 | Sub-task 1.1 | Sub-task |
| Project 1 | Sub-task 1.2 | Sub-task |
The 3-layer model (epic - task - subtask)
If you would like to create an epic with two tasks (one with 2 child items) and 2 subtasks like this:
- Epic 1
- Story 1.1
- Story 1.2
- Sub-task 1.2.1
- Sub-task 1.2.2
It is important to know:
- when you paste it into the ImpEx import dialog
- please make sure that you refer to the correct Project name
- always copy the column names too
- Sub-tasks are automatically assigned to the Story that are above them
- To have the storys assigned to an epic you will have to use the Epic name, the Issue ID and the Linked Issues columns.
(More about importing in general: Importing)
Please use this template
| Project | Summary | Issue Type | Epic Name | Issue ID | Linked Issues |
|---|---|---|---|---|---|
| Project 1 | Epic 1 | Epic | Epic 1 | 1 | is Epic of: 2 (Epic-Story Link); is Epic of: 3 (Epic-Story Link) |
Project 1 | Story 1.1 | Story | 2 | ||
| Project 1 | Story 1.2 | Story | 3 | ||
| Project 1 | Sub-task 1.2.1 | Sub-task | 4 | ||
| Project 1 | Sub-task 1.2.2 | Sub-task | 5 |
The 4-layer model (initative - epic - task - subtask)
If you already have initatives and you would like to create 2 epics in it with two tasks (one with 2 child items) like this:
- Initiative 1 (Issue Key = TP-1)
- Initiative 2 (Issue Key = TP-2)
- Epic 2.1
- Epic 2.2
- Story 2.2.1
- Story 2.2.2
- Sub-task 2.2.2.1
- Sub-task 2.2.2.2
It is important to know:
- You cannot create new initatives yet, you can only refer to an already existing one (but we are actively working on it)!
- Initatives were from Advanced Maps (formely Portfolio) add-on but now it is already built-in Jira itself: https://www.atlassian.com/software/jira/guides/roadmaps/advanced-roadmaps
PRO TIPP:
- You can connect Epics to initiatives with the help of the Parent Link column
- Parent Link import format: <Issue Key>
(More about importing in general: Importing)
| Project | Summary | Issue Type | Epic name | Issue ID | Linked Issues | Parent Link |
|---|---|---|---|---|---|---|
Project 1 | Epic 2.1 | Epic | Epic 2.1 | 1 | TP-2 | |
| Project 1 | Epic 2.2 | Epic | Epic 2.2 | 2 | is Epic of: 3 (Epic-Story Link); is Epic of: 4 (Epic-Story Link) | TP-2 |
| Project 1 | Story 2.2.1 | Story | 3 | |||
| Project 1 | Story 2.2.2 | Story | 4 | |||
| Project 1 | Sub-task 2.2.2.1 | Sub-task | 5 | |||
| Project 1 | Sub-task 2.2.2.2 | Sub-task | 8 |
, multiple selections available,
Related content
How to import linked issues?
How to import linked issues?
Read with this
Importing
Importing
Read with this
Importing
Importing
More like this
Import from Excel or Notepad
Import from Excel or Notepad
Read with this
Importing same-named custom fields
Importing same-named custom fields
Read with this
Exporting
Exporting
Read with this