Free Jira CSV import tool

Jira CSV Import Error Explainer

Paste a Jira CSV import error or warning and get a plain-English explanation with common causes, possible fixes and Jira configuration checks. No Jira access required.

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.

The matcher runs in your browser. The pasted error is not sent to an API and is not logged by this tool.

Common Jira CSV import errors

Choose a problem guide

Each guide explains the likely cause, possible fixes, Jira configuration checks and a safer way to prepare the next import.

Jira CSV Import Date Format ProblemsJira CSV date import can fail or skip values when CSV date values do not match the expected import or Jira date format.Jira CSV Import Empty Summary ErrorsJira issues need a summary or title, and your project may require additional fields before an issue can be created.Jira CSV Import Issue Type ErrorsThe issue type value must match an issue type available in the target project and must be mapped correctly.Jira CSV Parent-Child Import ProblemsParent-child imports depend on correctly mapped ID, key, type and parent fields, plus valid references that Jira can resolve.Jira CSV Import Sub-task ProblemsSub-tasks usually need a valid parent issue and the correct issue type before Jira can import them.Jira CSV Import User, Assignee and Reporter ErrorsJira may not resolve users if CSV values do not match users available to the site or project, or if the import expects a different identifier.Jira CSV Custom Field Import ProblemsCustom field values must match the field type and available options in the target Jira configuration.Jira CSV Priority, Status and Option Value ErrorsSelect-like values must match existing Jira options and workflow or status configuration.Jira CSV Duplicate Issue Key and Issue ID ProblemsDuplicate keys or IDs can cause skipped rows, conflicts, or unintended update behavior.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.Jira CSV Description, Comma and New Line ProblemsCSV values containing commas or line breaks may need quoting. Excel may hide these issues until the import preview parses columns differently.Jira CSV Labels, Components and Versions ProblemsMulti-value fields and project-specific options can require exact formatting and existing options.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.
Not ready to install a Jira app yet?

Start with the free checker

The checker runs locally in your browser and does not upload your CSV/XLSX file. You can identify common spreadsheet risks before deciding whether to install Excel to Jira Importer & Updater.

The checker is not a replacement for Atlassian's documentation or Jira's import preview. It is a practical preflight step for files that might contain empty summaries, duplicate keys, ambiguous dates or risky update fields.

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

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.

  • Map Excel columns to Jira fields safely.
  • Build Jira hierarchy from Excel with preview.
  • Review every Jira update before applying changes.

Jira CSV import error FAQ

Why does Jira CSV import fail?

Jira CSV import can fail when required fields are missing, values do not match Jira configuration, dates are in an unexpected format, users cannot be resolved, hierarchy references are invalid, or the CSV is parsed differently than expected.

Why are dates not imported correctly into Jira?

Dates may fail when the CSV date values do not match the import format or Jira settings. Avoid ambiguous dates and confirm parsed values in Jira's import preview.

How do I import parent-child relationships into Jira from CSV?

Parent-child imports usually require valid IDs, keys, issue types and parent references. The exact mapping depends on the Jira import experience and project configuration.

Why does Jira say a user was not found?

Jira may not resolve assignees, reporters or user picker values if the CSV uses the wrong identifier, the user lacks project access, or permissions prevent assignment.

Why does Jira reject custom field values?

Custom field values must match the field type, context and available options for the target project and issue type.

Can I update existing Jira issues from CSV?

Some import workflows can update existing issues when issue keys or identifiers are mapped intentionally. Always review the preview because duplicate keys and empty values can be risky.

Is CSV the safest way to bulk update Jira issues?

CSV can work, but it is fragile for bulk updates if fields, empty cells, duplicate keys and mappings are not reviewed carefully before changes are applied.

How can I check my CSV before importing to Jira?

Use the free readiness checker to inspect common spreadsheet risk signals locally in your browser, then review Jira's import preview before confirming the import.