Jira CSV import troubleshooting

Jira CSV parent-child import problems - how to fix

Parent-child imports depend on correctly mapped ID, key, type and parent fields, plus valid references that Jira can resolve.

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: Parent references do not match any existing issue or imported row.

Possible fix: Check that parent references exist or are included in the import.

Common causes

  • Parent references do not match any existing issue or imported row.
  • Issue IDs are not unique inside the CSV.
  • Parent and child rows use issue types that Jira does not allow together.
  • The required ID, key or parent columns are not mapped as expected.

How to fix it

  • Check that parent references exist or are included in the import.
  • Make every temporary issue ID unique.
  • Confirm sub-tasks have valid parent rows.
  • Map parent fields exactly as expected by your Jira import experience.

What to check in Jira

  • Hierarchy settings for the selected project.
  • Whether parent issues already exist or must be imported first.
  • Jira import wizard requirements for Issue Id and Parent fields.

Check your Jira configuration before importing. Field configuration, workflow, issue type scheme, permissions and import wizard behavior can change the result.

Example

Issue Id,Parent Id,Issue Type,Summary
EPIC-1,,Epic,Checkout improvements
STORY-1,EPIC-1,Story,Guest checkout
SUB-1,STORY-1,Sub-task,Add form validation

How to avoid this next time

  • Unique row IDs
  • Valid parent references
  • Hierarchy allowed by Jira configuration

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.

Try it for free Try the free readiness checker Watch the short demo

Related Jira CSV import errors

Jira CSV Import Sub-task ProblemsSub-tasks usually need a valid parent issue and the correct issue type before Jira can import them.Jira CSV Import Issue Type ErrorsThe issue type value must match an issue type available in the target project and must be mapped correctly.Jira CSV Duplicate Issue Key and Issue ID ProblemsDuplicate keys or IDs can cause skipped rows, conflicts, or unintended update behavior.Free Jira CSV and Excel readiness checkerNo Jira access required. Check CSV risk signals and basic workbook metadata locally in your browser.