"Unable to parse date" error using CSV import in Jira Cloud

Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.

Summary

You may encounter "Unable to parse date" Error of fatal error using CSV import in Jira Cloud

Cause

The date format set in the CSV file doesn't match the date format set during the CSV import.

Solution

During the 'Setup' step of the import process, it's important to include the same date format used in your CSV file. Make sure to apply this format consistently for all date fields in the file.

You can refer to this page to get the syntax for your date fields: SimpleDateFormat

Example 1

In the CSV file, you are using the following date format:

1 23/02/2023 08:54

Datetime in CSV

Correct date format pattern

23/02/2023

dd/MM/yyyy

23/02/2023 08:54

dd/MM/yyyy HH:mm

During the import process, in the Setup step, you should set the date format to match the format set in the CSV file:

(Auto-migrated image: description temporarily unavailable)

Example 2

You receive and error of:

Unable to parse datetime: 31/May/23 using the date format pattern: dd/MMM/yy h:mm a

Cause: In this case the date time `31/May/23` does not match the date format pattern `dd/MMM/yy h:mm a` because it is missing the `h:mm a`. To fix this you need to change the date format pattern to `dd/MMM/yy`

Datetime in CSV

Correct date format pattern

31/May/23

dd/MMM/yy

31/May/23 12:08 PM

dd/MMM/yy h:mm a

Example 3

Unable to parse datetime: 31-May-23 using the date format pattern: dd/MMM/yy

Cause: The input date uses dashes instead of slashes. The date format pattern needs to be changed to dd-MMM-yy

Datetime in CSV

Correct date format pattern

31-May-23

dd-MMM-yy

31/May/23

dd/MMM/yy

Example 4

Unable to parse datetime: 31/May/23 0:00 a using the date format pattern: dd/MMM/yy h:mm a

Cause: 0 is invalid value when used in the AM/PM time format. If using the AM/PM format, 0 hours would need to be converted into 12

Datetime in CSV

Correct date format pattern

31/May/23 0:00 a

n/a - invalid datetime

31/May/23 12:00 AM

dd/MMM/yy h:mm a

Updated on April 11, 2025

Still need help?

The Atlassian Community is here for you.