Jira Introduces New Options for Mapping Issue Types and Hierarchies

Atlassian, the company behind the popular software ‘Jira’ has rolled out an update that provides more control over how issue types are mapped when importing data from external sources. The new feature allows users to assign specific issue types—such as Epic, Task, Story, Bug, or Subtask—during the import process, eliminating the previous limitation where all imported issues defaulted to the “Task” type. Here’s everything you need to know.

Maintaining Hierarchies in Imported Data

The update improves how hierarchical relationships are managed during imports. It now allows users to include columns in their CSV files to specify parent-child relationships between issues. By mapping columns such as “Issue ID” and “Parent,” imported data retains its original structure, which is particularly useful for large projects with multiple dependencies.

How to Use the New Import Features 

• Prepare your CSV file and make sure it is ready for import. Each row of data should represent a new issue, and each column should represent a Jira field associated with that issue.

• Map Project Fields On the “Map Project Fields” screen, you can map the columns in your CSV file to specific Jira fields. For example, you can classify an issue as a specific issue type by mapping a column to the “Issue Type” field.
• During the import, you can choose from standard issue types (Epic, Task/Story/Bug, Subtask) or create custom issue types.

• If your issues already have a parent-child relationship, you can import it by including two columns that represent the relationship (Issue ID and Parent). Map these columns to the “Issue ID” and “Parent” fields to ensure the hierarchies are imported correctly.
• Once you’ve mapped them, review them on the Review Details screen to confirm everything is set up correctly before importing.

• Click “Import” to start the import process. The new importer will set up and map your issue types and hierarchies in Jira.

Note: The new import feature is now available for Jira Software Cloud users.  

More Flexible Data Import Process 

Earlier, this process was quite cumbersome, as the system automatically assigned all imported items as “Tasks,” forcing you to manually adjust them afterward. However, with the latest update, you can now map issue types directly from their CSV files, ensuring a more structured import process.

Moreover, Jira now allows the creation of custom issue types at the time of import. This means that if an issue type does not exist in the destination project, you can define and apply a new one without needing to exit the import workflow. 

This update can be a savior if you are someone who struggles to manage and import data. As teams can now import data without losing essential information related to issue type and structure, reducing the need for post-import adjustments.