Map column data to issue types

In the new import experience, you can connect the information within a specific column from your CSV file to issue types in Jira. Read about issue types

Issue types help build structure in your project planning and the default issue types in Jira can vary based on the type of project you select. You can also establish hierarchies between issues. Jira has three levels of issue-type hierarchy by default:

• Epic (level 1)

• Task/Story/Bug (level 0)

• Subtask (level -1)

Make sure to set up the issue hierarchy in your CSV file to match the structure in Jira. More about preparing your CSV file before import

Structure your issue hierarchy

Based on your Jira plan, you can either map to default Jira issue types or create new issue types during the import. Here are the import capabilities available for each Jira plan:

Map CSV column to issue type field

When importing data into Jira using a CSV file, each row of data from the CSV file will be imported as an issue into your new project in Jira. In the Map project fields screen, all the column headers from the CSV file are listed and will need to be mapped to Jira fields.

To import issue types, you must map a column from the CSV file to the issue type field in the Map project fields screen. If you’d like to establish hierarchy levels, map columns to issue ID and parent fields in addition to the issue type field. The issue ID and parent information helps bring in the “parent” and “child” relationships among issues. The values within the column mapped to the issue type field can be mapped to specific Jira issue types in the next screen (Map values to issue types).

Map values to Jira issue types

In the Map values to issue types screen, values from the CSV column mapped to the issue type field are listed. If there are duplicate values in the column, they will be combined as a single line item on this screen. You will need to map these values to different Jira issue types. If you have more than 150 unique values, you will be notified to check if the right column from the CSV file is mapped to the issue type field.

To map CSV column values to Jira issue types:

1. Select the dropdown next to the CSV column value you want to map and choose an existing or suggested Jira issue type or create a new issue type.

2. If you select Create a new issue type, you can create a custom issue type in two levels: Standard (level 0) or Subtask (level -1).

   1. Once you select an issue type level, a custom issue type will be created with the same name as the value from the CSV column.

3. Select Next once all the values are mapped to issue types.

If the column values are incorrectly mapped to issue types, you will see an error. This occurs when the hierarchies established among issues in the CSV file are disrupted. To fix the error, map column values to issue types at the same level. For instance, a level 0 value can only be mapped to level 0 issue types like task, bug, and story.

The number of issue types in your new project will be displayed in the Review details screen. By default, any unmapped values will be mapped to Task (level 0). Once the data is imported, your issues will be assigned the selected issue types, and the child issues will be displayed within parent issues in the issue view.