Jira CSV import troubleshooting

Jira CSV import date format problems - how to fix

Jira CSV date import can fail or skip values when CSV date values do not match the expected import or Jira date format.

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 uses more than one date format in the same column.

Possible fix: Use one consistent date format across the whole column.

Common causes

  • The CSV uses more than one date format in the same column.
  • The import wizard expects a different date or date/time pattern.
  • Dates such as 01/02/2026 are ambiguous across regions.
  • Excel exported dates differently from the values shown in the workbook.

How to fix it

  • Use one consistent date format across the whole column.
  • Avoid ambiguous dates such as 01/02/2026.
  • Check the date format selected in the import wizard and Jira settings.
  • Use Jira's import preview to confirm parsed date values before continuing.

What to check in Jira

  • Date and date/time fields available for the target project and issue type.
  • The date format selected in the Jira import wizard.
  • Project locale and Jira date settings that may affect parsing.

Check your Jira configuration before importing. Field configuration, workflow, issue type scheme, permissions and import wizard behavior can change the result.

Example

Summary,Due date
Renew supplier contract,2026-07-31
Prepare release notes,2026-08-14

How to avoid this next time

  • One date format per column
  • No ambiguous day/month values
  • Date fields mapped 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.

Preview Excel date values before importing to Jira

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.

Try it for free Try the free readiness checker Watch the short demo

Related Jira CSV import errors

Jira CSV Import Field Mapping ProblemsField mapping problems happen when Jira cannot connect CSV columns to the Jira fields needed for the selected project and issue type.Jira CSV Custom Field Import ProblemsCustom field values must match the field type and available options in the target Jira configuration.Jira CSV Bulk Update RisksCSV files with issue keys may be treated as update-like workflows depending on the import method. Empty values and duplicate keys can be risky.Free Jira CSV and Excel readiness checkerNo Jira access required. Check CSV risk signals and basic workbook metadata locally in your browser.