Troubleshooting creating issues in hierarchy via CSV Import in Jira
Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.
Summary
This article outlines different scenarios for creating issues within a hierarchy level in Jira Cloud.
Solution
Scenario 1: Creating Both Parent and Child Issues Simultaneously
If both the parent and child issues are being created at the same time, include the following fields in your CSV:
Summary: Mapped to Summary
Issue Type: Mapped to Issue Type
Issue ID: Mapped to Issue ID
Parent ID: Mapped to Parent
The parent and issue IDs are unique random numbers used by the importer to link the issues together and do not reflect the actual issue IDs in the database.
Example CSV Format:
1
2
3
Summary, Issue Type, Issue ID, Parent ID
Test, Task, 1,
Test, Sub-task, 2,1Scenario 2: Creating Only Child Issues
If only the child issues exist in the CSV file, ensure the following fields are included:
Summary: Mapped to Summary
Issue Type: Mapped to Issue Type
Issue ID: Mapped to Issue ID
Parent ID: Mapped to Parent (Holds the issue key of the existing parent issue)
Example CSV Format:
1
2
Summary, Issue Type, Issue ID, Parent ID
Test, Sub-task, 1, ABC-123By following these guidelines, you can ensure that your CSV import process for creating issues in Jira Cloud is successful.
Was this helpful?