Jira CSV duplicate issue keys and issue IDs - how to fix
Duplicate keys or IDs can cause skipped rows, conflicts, or unintended update behavior.
This is not official Atlassian documentation. Your Jira import wizard and project settings may behave differently. Always review Atlassian's current documentation and your Jira import preview before confirming an import.
Short explanation
Common cause: The file contains repeated Issue Key or Issue Id values.
Possible fix: Decide whether the file is meant to create or update issues.
Common causes
- The file contains repeated Issue Key or Issue Id values.
- A create import includes keys that already exist in Jira.
- A file intended for updates is being used as a create import.
- Temporary hierarchy IDs are reused across rows.
How to fix it
- Decide whether the file is meant to create or update issues.
- Ensure keys and IDs are unique where Jira expects uniqueness.
- Remove accidental duplicate rows before import.
- Map identifiers only when you intentionally need them.
What to check in Jira
- Whether the selected import method creates or updates issues.
- Issue keys already existing in the target Jira site.
- Duplicate handling in the import preview.
Check your Jira configuration before importing. Field configuration, workflow, issue type scheme, permissions and import wizard behavior can change the result.
Example
Issue Key,Summary
PROJ-100,Update pricing copy
PROJ-100,Duplicate row that needs reviewHow to avoid this next time
- No accidental duplicate keys
- Create/update mode understood
- Identifier mapping intentional
No Jira access required: the free checker can help identify common spreadsheet risks locally in your browser before you decide whether to install a Jira app.
Review every Jira update before applying changes
CSV imports are possible, but fragile. Excel to Jira Importer & Updater lets you map real Excel workbooks, clean values, create or update Jira issues, and review every change before Jira is modified.