Jira CSV import Summary is required - how to fix
Jira issues need a summary or title, and your project may require additional fields before an issue can be created.
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: Some rows have an empty Summary value.
Possible fix: Check empty Summary values in the CSV.
Common causes
- Some rows have an empty Summary value.
- The header row was not detected correctly.
- The Summary column was not mapped to Jira Summary.
- The target project requires additional fields beyond Summary.
How to fix it
- Check empty Summary values in the CSV.
- Confirm the correct header row and delimiter.
- Map the Summary column explicitly.
- Fill required fields for every row or adjust the target project configuration.
What to check in Jira
- Required fields for the selected project and issue type.
- Field configuration and screen configuration.
- Jira import preview warnings for unmapped or empty required fields.
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,Description
Prepare onboarding checklist,Task,Create a first draft
,Bug,This row will likely failHow to avoid this next time
- No blank Summary cells
- Correct header row
- Required Jira fields mapped
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.