Jira CSV import field mapping problems - how to fix
Field mapping problems happen when Jira cannot connect CSV columns to the Jira fields needed for the selected project and issue type.
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 header row is wrong or shifted.
Possible fix: Confirm the header row and delimiter.
Common causes
- The header row is wrong or shifted.
- Important columns are not mapped.
- Two columns appear to represent the same Jira field.
- The selected project or issue type changes which fields are available.
How to fix it
- Confirm the header row and delimiter.
- Map required Jira fields deliberately.
- Remove columns you do not intend to import or update.
- Use the preview to verify final field values.
What to check in Jira
- Fields available for the target project and issue type.
- Required fields in the target field configuration.
- Jira preview of mapped and unmapped columns.
Check your Jira configuration before importing. Field configuration, workflow, issue type scheme, permissions and import wizard behavior can change the result.
Example
Summary,Issue Type,Priority,Due date
Prepare pilot import,Task,Medium,2026-07-31How to avoid this next time
- Header row confirmed
- Required fields mapped
- Unused columns ignored
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.
Map Excel columns to Jira fields safely
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.