Documentation for JIRA 4.2. Documentation for other versions of JIRA is available too.

Skip to end of metadata
Go to start of metadata


This page answers some of the commonly asked CSV questions our technical support staffs have encountered. If you are not able to find an answer from this page and our issue tracker, feel free to create a support issue.

For more information about JIRA's built-in CSV Importer, please refer to this page.

Commonly Asked Questions

The importer simply doesn't work on my CSV file!

Please make sure that it is a valid and not-bad-formatted CSV file. You should be able to spot this with by turning on detailed logging and profiling. Also, please double check your configuration file and ensure that it's properly configured, e.g. exact delimiter, date format, etc.

The importer fails at date fields, why?

If you are seeing error message similar to this:

[00:55:28] FAILED: Customfield value 01/Nov/06 12:00 AM is invalid
[00:55:28] com.atlassian.jira.issue.customfields.impl.FieldValidationException: Invalid date format. Please enter the date in the format "MMM/dd/yy".
at com.atlassian.jira.issue.customfields.converters.DatePickerConverter.getTimestamp(
at com.atlassian.jira.issue.customfields.impl.DateCFType.getSingularObjectFromString(
at com.atlassian.jira.imports.importer.impl.DefaultJiraDataImporter.importIssues(
at com.atlassian.jira.imports.importer.impl.DefaultJiraDataImporter.doImport(

There are a few possible reasons:

  • Date format is not correctly set in the import configuration file
  • Date Picker and Date Time Picker formats are not consistent, e.g. hh:mm a
    should be corrected to, hh:mm a

Why does the importer always ask me to map values to column (at Step 3 of 5)?

It is because you have selected Map Field Value for the particular columns. To use the values from the CSV, you need just to map the column to the Corresponding JIRA field, otherwise, select the Map field value checkbox.

Why doesn't the importer recognize the extra columns for comments?

This is actually a known issue being raised at JIM-71. Please try the workaround as suggested in the issue. Alternatively, you can write your own comment mapper for more flexibility to meet your requirements.

Known Issues

Why couldn't I import issues with other languages?

Setting the -Dfile.encoding=utf8 parameter should be able to fix your problem. Otherwise, you may like to vote for this issue at JIM-232.

Why couldn't I import from cascading select fields?

This is an open issue being tracked at JIM-231. Feel free to comment and vote on it.

Why couldn't I create subtasks?

This is an open issue being tracked at JIM-230. Feel free to comment and vote on it.

Why couldn't I import component/version Custom Fields?

This is an open issue being tracked at JIM-233. Feel free to comment and vote on it.