Commonly asked CSV questions and known issues
This page answers some of the commonly asked CSV questions our technical support staff 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.
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".
There are a few possible reasons:
- The format of dates is not correctly set in the import configuration file. The date format for custom fields must match the "Date format in input file" which has a default format of yyyyMMddHHmmss
- Jira system date fields such as Created, Updated and Due Date use "yyyy-MM-dd HH:mm:ss" but may need an offset adding
Date Picker and Date Time Picker formats are not consistent, e.g.
jira.date.picker.java.format=dd/MMM/yy jira.date.time.picker.java.format=MMM/dd/yy hh:mm a
should be corrected to,
jira.date.picker.java.format=dd/MMM/yy jira.date.time.picker.java.format=dd/MMM/yy 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.
There is a known problem that prevents the CSV Importer from being used with Jira instances running on JBoss 4.x. This is due to a compatibility issue between the JBoss 4.x commons-collections.jar and the Jira commons-collections.jar. The workaround is to replace the commons-collections.jar in JBoss 4.x with the more recent Jira version. Please see JRA-6473 for further details.