How to import parent-child related issues?
- Kojnok Roberta
Owned by Kojnok Roberta
Sept 07, 2020
1 min read
Loading data...
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 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: Import from Excel or Notepad)
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) 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 JExcel 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: Import from Excel or Notepad)
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 |