Enhance Your Jira Imports: New Options for Mapping Issue Types and Hierarchies
Hello, Atlassian Community!
I am Shruti Narayan, Product Manager for the importers feature, and I am excited to announce the general availability of new options for mapping issue types.
As part of the new import experience, administrators can now seamlessly setup and map various issue types and hierarchies when importing data from other project management tools to Atlassian products. This capability ensures smoother data ingestion and integration into Jira.
Previously, when importing data from a .CSV file, all issues were automatically set as the default Jira issue type, which was a task. Now, you can select the appropriate Jira issue types—such as epic, task, story, bug, or subtask—for your team’s work. Additionally, you can create custom issue types during the import. This enhancement gives you better control over assigning issue types and helps establish parent-child relationships between tasks, improving project organization in Jira.
What’s new?
When importing data into Jira, each row of data from the .CSV file will be treated as a new issue associated with the latest project in Jira. Each column will represent a Jira field associated with that particular issue.
Import Issue Types
On the "Map Project Fields" screen, you can map the columns to a specific Jira field. Now, you can classify an issue as a specific issue type by mapping a column in your CSV file that represents issue types in the “Issue Type" field.
Import parent-child relationships
It’s worth noting that if the issues you’re importing already have a parent-child relationship, you can import that relationship by including two columns that represent details of the relationship, mapping them to the “Issue id” and “Parent” fields, codifying the relationship between imported issues.
The two fields are required because “Issue id” helps identify each issue. “Parent” helps identify the parent relationship and is simply the issue ID of the parent issue. Ensure the IDs are unique to each issue to ensure the hierarchies are imported.
Map to existing issue types or create custom issue types
Once you’ve mapped the issue type field, you can map the values from the column you’re using to represent issue types to those in Jira. For example, standard issue types include:
-
Epic (level 1)
-
Task/Story/Bug (level 0)
-
Subtask (level -1)
Additionally, based on your Jira plan, you can create new issue types during the import!
Review your issue types before import
Once you’ve mapped your issue types, you can review how they’ll be imported in the Review Details screen.
Share your feedback
To know more about this feature, read our support documentation.
We hope this feature will improve your import journey. We’d love to hear your thoughts and ideas. Please share them below, and let’s keep the conversation going.
Was this helpful?
Thanks!
Shruti Narayan
2 comments