Prepare a CSV file for import

Comma-separated value (CSV) files are text files that represent tabulated data and are supported by most systems that handle tabulated data, such as spreadsheets and databases. You can base the structure of your CSV file on the default Microsoft Excel CSV format.

Here are a few tips to help you prepare your CSV file in order to move data using the new import experience.

Tips for preparing your CSV

Include a heading row with a summary field

When importing a file, the summary field is always required. It provides an overview of the issue.

The summary field is a short description of an issue that is used to provide a quick overview of what the issue is about. It is typically the first piece of information you’ll see when browsing issues. The field should be concise and descriptive and should provide enough information to understand the nature of the issue.

The CSV importer uses the file header row to determine how to map data from the file's 2nd row and beyond to fields in Jira.

Assign users to issues

Use email addresses when adding people as assignees, reporters, or creators to your CSV file. This will help us map them to the project and issues created. Read about importing CSV data into Jira fields

If a CSV file doesn’t contain email addresses in user fields, you can manually add email addresses to the relevant user IDs during the import.

Avoid punctuation in the header row

To prevent inaccuracies in your imports, avoid including any punctuation in the header row (apart from the commas separating each column).

Mention users in the description or comments of an issue

To use mentions in the description or comment fields of an issue, replace the user mention in your data with the following email-based mention format: [~email:user@example.com]
Once imported, the mention will be linked to the user associated with the provided email address.

Structure data for comments within an issue

To ensure your comments are imported correctly, structure data in comments in this manner:

If the data isn’t structured in this format, the comment creator’s name will display as Anonymous.

Treat special characters literally

Use double-quote marks (") around a section of text to treat any special characters in that section literally. Once this data is imported, these special characters will be stored as part of Jira's field data. Examples of special characters include carriage returns/enter characters, commas, etc.

To treat a double quote mark literally, you can add another double quote mark character:

...which, once imported, will be stored in Jira as:

Aggregate multiple values into single-issue fields

You can import multiple values into a single Jira field that accepts multiple values (e.g. Watchers, Component, Labels). To do this, your CSV file must specify the same column name for each value you wish to import to the same field. The number of column names specified must match the maximum number of values to be aggregated into the mapped field.

For example:

In the above example, the Label and Component fields in the first issue and the Component field of the third issue will generate multiple values in the relevant field after importing.

Keep the organization names less than or equal to 200 characters

While importing a CSV file into a Jira Service Management project, keep the names of your organization equal to or less than 200 characters. If the organization name is greater than 200 characters, you will see an error while mapping your data for import.

Add reporters column to your CSV file for a service project

Service projects have request types attached to the issues. These request types are dependent upon the reporters column in the service project.

While importing data from your CSV file, add the reporters column to ensure a smooth import of your issues.

Assign issue types to request types in service projects

While importing data from a CSV file into a service project, each issue type is mapped to a request type and issue status.

Make sure to change the issue types in the CSV file based on the request type you’d like to assign to. If the issue type is TASK, SUBTASK or any other value, the request type will default to NO REQUEST TYPE. If the issue type is GENERAL REQUEST, the default request type EMAILED REQUESTwill be assigned.

If there is no default status assigned, issues will be assigned IN PROGRESS status.

Handle custom fields

When importing data into your business or software project you can choose to create new custom fields. Custom fields allow you to add information specific to your team's needs. You can also import data to a variety of existing custom fields created previously within your instance.