Hierarchy import

Import Jira hierarchy from Excel

Use Excel to Jira Importer to prepare parent-child structures from Excel columns, validate the setup and review the result before creating or updating Jira issues.

The problem

Hierarchy is easy to understand in Excel but hard to import safely. Parent rows, child rows, grouping columns and issue relationships need to be mapped and validated before Jira issues are created.

The solution

Use a reviewed hierarchy import flow:

Example workflow

Excel: Epic / Story / Task / Parent reference

Jira: Mapped issue structure based on supported Jira fields, app functionality and your Jira project configuration.

Import structured Excel backlogs into Jira

Review parent-child relationships and issue types before creating selected Jira issues.

Early launch offer: help with your first Excel-to-Jira import

Trying a new Jira import app is easier when the first real file works. During the early launch period, we help trial users prepare their first Excel-to-Jira import by email. Send a sanitized workbook, column list or screenshots, and we will help you choose the right worksheet, header row, field mapping, cleanup rules and validation approach before you import.

No video call is required. You stay in control of the import, and nothing changes in Jira until you review and confirm it in the app. Please avoid sending confidential customer data unless your organization allows it. A small anonymized sample is usually enough.

Get help with your first import

Email: support.jira@mederak.app

Related resources

FAQ

Can I import parent-child relationships from Excel?

Yes, when the workbook contains the needed parent references or hierarchy columns and Jira allows the resulting relationships.

Can I map issue types from Excel columns?

Yes. The app can use issue type mapping, subject to Jira project configuration and validation.

Can I preview hierarchy before import?

Yes. Validation and preview help check hierarchy before Jira issues are created or updated.

What happens if a parent reference is missing?

Validation reports the problem so the data or mapping can be fixed before import.

Does this support my Jira project configuration?

Hierarchy behavior depends on issue types, parent rules, screens and permissions in the selected Jira project.