Jira CSV import issue type errors - how to fix
The issue type value must match an issue type available in the target project and must be mapped correctly.
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 contains values that do not exist in the target project.
Possible fix: Normalize values such as Task, Bug, Story and Sub-task.
Common causes
- The CSV contains values that do not exist in the target project.
- Values have extra spaces or inconsistent casing.
- Sub-task values are mixed with standard issue type values.
- The issue type column is missing or not mapped.
How to fix it
- Normalize values such as Task, Bug, Story and Sub-task.
- Check which issue types are available in the target project.
- Map the issue type column intentionally.
- Separate sub-task imports if the import flow requires a parent reference.
What to check in Jira
- Project issue type scheme.
- Issue type values accepted by the CSV import wizard.
- Whether sub-tasks are enabled and available in the project.
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
Fix login redirect,Bug
Write onboarding page,Task
Add password reset tests,Sub-taskHow to avoid this next time
- Issue type values normalized
- Issue type column mapped
- Sub-task rows have parents
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.
Import real Excel workbooks into Jira with mapping, cleanup and review
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.