Import work into an existing space in Jira using CSV
Learn how to import work items or update existing work items in an existing space in Jira using CSV files.
Important limitations
A few things you should know:
Only CSV imports are supported for this feature.
Jira Service Management spaces aren’t supported. You can only import into existing Jira Software and Jira Work Management spaces.
When you’re updating existing work items:
you can’t update some fields through CSV import: Reporter, Resolution, Resolved date, Watchers, Voters, and Security level
Status and Priority values in your CSV must match existing values configured in your space; unmapped or invalid values will lead to import failures
Import work items into an existing Jira space
Site and organization admins can import content into both company-managed and team-managed spaces. Other users can import content only into team-managed spaces.
To import work items into a Jira space using a CSV:
Select Settings (), then System. Then, select External system import.
Or, if you’re not an admin, hover over Spaces in the sidebar and select Create space (), then select Import data.
Select System then External System Import.
Select CSV as the import source.
Select the existing Space you want to import work items into.
Upload your CSV file.
Map the fields in your CSV file to the fields in your existing Jira Space. All fields, statuses, work types, and custom fields must already exist in the space.
To update existing work items, make sure your CSV contains an Work item Key column populated with the keys of the work items you want to update (for example, `PROJ-123`), and map this column to the Work item Key field in Jira. Rows matching existing issues in your space will update supported fields on those issues. Any other rows such as those without a work item key or with unmatched rows will be created as new work items.
In case of CMP projects, you can create new work types, custom fields, and custom field options, if required. More about mapping CSV data to Jira fields
Make sure to select the appropriate hierarchy level from the dropdowns. More about mapping column data to work types
You can only map to existing statuses and priorities. New ones can’t be created. You can a create new status/priority manually in Jira after the import.
If no statuses are mapped, a default status will be automatically picked.
In case of TMP projects, all fields, statuses, work types, and custom fields must already exist in the space.
Review the migration summary. If your CSV contains new statuses or priorities that aren’t present in your existing space, the import will fail. Resolve these conflicts before proceeding.
Start the import process.
After the import completes, review the migration report.
No new configuration elements can be added during import.
Was this helpful?