Jira CSV priority, status and option value errors - how to fix
Select-like values must match existing Jira options and workflow or status configuration.
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 CSV value has different casing or trailing spaces.
Possible fix: Normalize casing and remove trailing spaces.
Common causes
- The CSV value has different casing or trailing spaces.
- The option exists in another project but not the target project.
- The status is not valid for issue creation or the current workflow.
- Resolution values are mapped when they should be left empty for open issues.
How to fix it
- Normalize casing and remove trailing spaces.
- Make sure options exist in the target Jira configuration.
- Avoid mapping workflow status unless the import method supports it.
- Check the preview for invalid option warnings.
What to check in Jira
- Priority scheme and project options.
- Workflow statuses available for the issue type.
- Resolution values and whether they are appropriate for the import.
Check your Jira configuration before importing. Field configuration, workflow, issue type scheme, permissions and import wizard behavior can change the result.
Example
Summary,Priority,Status
Fix payment retry,High,To DoHow to avoid this next time
- Options exist in Jira
- No trailing spaces
- Workflow values reviewed
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.