Jira CSV custom field import problems - how to fix
Custom field values must match the field type and available options in the target Jira 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 custom field is not available for the target project or issue type.
Possible fix: Check field context and project availability.
Common causes
- The custom field is not available for the target project or issue type.
- Select values do not exactly match configured options.
- Multi-select values use a separator Jira does not interpret as intended.
- Cascading select values are missing the parent or child option.
How to fix it
- Check field context and project availability.
- Match option names, casing and whitespace exactly.
- Confirm formatting for multi-value fields.
- Preview the import before making Jira changes.
What to check in Jira
- Custom field context.
- Project and issue type field configuration.
- Allowed options for select, multi-select and cascading select fields.
Check your Jira configuration before importing. Field configuration, workflow, issue type scheme, permissions and import wizard behavior can change the result.
Example
Summary,Customer tier,Regions
Renew platform contract,Enterprise,"EU, US"How to avoid this next time
- Field exists in target context
- Options match Jira
- Multi-values formatted deliberately
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.