Get started with Jira Work Management
New to Jira Work Management? Check out our guides for new administrators and users.
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.
When creating a CSV file that can be imported into Jira Work Management, make sure all fields are separated by commas and that any piece of content, including commas and new lines, is enclosed in quotes. Learn more about specific file requirements and data structure
When importing a file, the summary field is always required and is the field that 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 Work Management.
If you’re importing data that includes parent and subtasks other fields may also be required depending on the configuration of your instance. Learn more about creating issues and subtasks
Use an email address or Atlassian Account ID when adding people as assignees, reporters, or creators etc. to your CSV file. This will help us map them to the project and issues created within the imported business project. Learn more about importing CSV data into Jira fields
Avoid including any punctuation in the header row (apart from the commas separating each column), to prevent inaccuracies in your imports.
Use an email address or Atlassian Account ID when adding people as assignees, reporters, or creators. This will help us add them to the project and the tasks created within this project.
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:
1
"Clicking the ""Add"" button results in a page not found error"
...which, once imported, will be stored in Jira as:
1
Clicking the "Add" button results in a page not found error
You can import multiple values into a single Jira field that accepts multiple values (e.g. Fix (for) Version, Affects Version, 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:
1
2
3
4
IssueType, Summary, FixVersion, FixVersion, FixVersion, Component, Component
bug, "First issue", v1, , , Component1,
bug, "Second issue", v2, , , Component1, Component2
bug, "Third issue", v1, v2, v3, Component1,
In the above example, the Component field of the second issue and the Fix Version field of the third issue will generate multiple values in the relevant field after importing.
When importing data into your business project you can choose to create new custom fields. Custom fields allow you to add information specific to your team's needs. Learn more about creating custom fields
You can also import data to a variety of existing custom fields created previously within your instance.
Was this helpful?