Jira CSV import sub-task problems - how to fix
Sub-tasks usually need a valid parent issue and the correct issue type before Jira can import them.
This is not official Atlassian documentation. Your Jira import wizard and project settings may behave differently. Always review Atlassian's current documentation and your Jira import preview before confirming an import.
Short explanation
Common cause: Sub-task rows do not include a parent reference.
Possible fix: Add parent references for every sub-task row.
Common causes
- Sub-task rows do not include a parent reference.
- The parent issue is not included in the import and does not already exist.
- The issue type value does not match the Jira sub-task type.
- The target project does not allow the intended sub-task relationship.
How to fix it
- Add parent references for every sub-task row.
- Import parent issues first or include them in the same structured import.
- Normalize the sub-task issue type value.
- Check Jira's preview for parent resolution warnings.
What to check in Jira
- Whether sub-tasks are enabled.
- Available sub-task issue types.
- Parent issue visibility and permissions.
Check your Jira configuration before importing. Field configuration, workflow, issue type scheme, permissions and import wizard behavior can change the result.
Example
Parent Key,Issue Type,Summary
PROJ-123,Sub-task,Write edge case tests
PROJ-123,Sub-task,Update field labelsHow to avoid this next time
- Every sub-task has a parent
- Parent key exists or is imported
- Sub-task type is valid
No Jira access required: the free checker can help identify common spreadsheet risks locally in your browser before you decide whether to install a Jira app.
Build Jira hierarchy from Excel with preview
CSV imports are possible, but fragile. Excel to Jira Importer & Updater lets you map real Excel workbooks, clean values, create or update Jira issues, and review every change before Jira is modified.