Formatters & Code

Jira CSV Hierarchy & Parent Checker

Check Jira CSV parent references, duplicate IDs, cycles and import ordering locally. Explore a visual hierarchy preview and download review reports.

Issue CSV & hierarchy settings

Issue CSV

Up to 10 MB, 20,000 issues and 100 columns. Include Summary, Issue type, Parent and your chosen identifier column.

Import profile Parent references use

The Cloud ID profile follows Atlassian's documented external-system workflow, which currently directs users to the old import experience. Select structural checks for a different importer, team-managed project or Data Center; confirm that workflow separately.

Require parents before their children

Issue-type levels and pre-existing parents

Issue-type levels (one Type=level per line)Higher numbers are above lower numbers. These are editable review assumptions, not a copy of your Jira configuration. Unknown types receive a warning. Declared pre-existing parent references (optional)Use the selected reference format. These declarations receive warnings; their existence is never verified.

Results

What the result means

Export your issue spreadsheet as a UTF-8 CSV and choose the import profile that matches your workflow. The documented Cloud external-system profile checks numeric Issue ID references; other importers use structural checks with an explicit reference field. Review the issue-type level map, then run the checker. It builds a local relationship graph, identifies ambiguous identifiers and broken links, and shows an expandable preview. Declare any pre-existing parents separately so they remain visibly unverified. Download the findings and hierarchy reports for review. Nothing is sent to Jira, and the checker cannot confirm destination permissions, project configuration or whether an external parent exists.

Related tools

Guides

Questions

Does this use Epic Link to build Jira Cloud hierarchies?

No. The preview uses the Parent column. Legacy Epic Link columns are reported for review rather than automatically translated.

What is the difference between Issue ID and Issue key?

They are distinct identifiers. The Cloud external-system profile uses numeric IDs; structural mode lets you select the reference format your importer expects.

Can my parent already exist in Jira?

Declare its reference in the optional existing-parent list. It remains unverified because this tool has no account connection. Confirm it in the destination project before import.

Can this check a different Jira importer?

Use structural mode to inspect the graph with your chosen reference and ordering settings. It does not reproduce importer-specific behaviour or certify a deployment.