Dates are not properly imported from CSV file to Jira

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform Notice: Cloud, Server, and Data Center - This article applies equally to all platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

A CSV file's date format must match Jira's Complete Date/Time Format and the date format in the CSV import interface. If these don't match, dates can be malformed or completely skipped during import.

Confirm Jira's setting for date and time

Jira has a configuration option for how dates and times are formatted in the user interface. You can confirm the setting by clicking the upper-right Settings Cog > System > Look and Feel.

Check the format used for Complete Date/Time Format. Your CSV file must also use this format to prevent errors upon import.

Prepare the CSV file for import

If you have multiple date formats in the CSV file, convert all of them to only use a single format.

In the import setup screen make sure you choose the right date format that matches exactly what you have in your CSV. 

If you want to inspect your file's formatting, be sure to look at the date in a plain text editor. Spreadsheet editors like Microsoft Excel will automatically reformat the date, instead of displaying the raw information.

If you wish to import issue dates to system fields, such as created, updated, or resolved, make sure you select Issue Fields and not Custom Fields in the importer. 


Last modified on Nov 13, 2024

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.