nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Unable to use Jira csv import for date with May and October

Moez SAID

Hello,

When I use the dd/MMM/yy format in the import configuration file, all dates are recognized by JIRA except those of May and October
Example 01/May/21, JIRA shows this error message "Unable to parse date: 01/May/20"
The same problem occurs with the month October
Please note that the import works fine if I replace "May" or "Oct" with any other month. Exemple (01/Apr/21)
I need to import dates in this format (dd/MMM/yy) because my import file (it's an export from another JIRA instance) contains dates of the same format in the user comments columns as well as in the attachments columns, and I have to adapt the date fields (created, updated, Due, ...) to this format to avoid updates after the creation import.
Do you have any idea about this problem?

Thanks in advance!

Best regards

Accepted answers

All comments

Radek Dostál

Excel can be deceiving, because it is trying to know better than the user and change their data to "personalize" their experience.

There isn't any known bug or problem with specific months (there is with 'Target start' and 'Target end', but those are specific Roadmaps fields), the problem is likely somewhere in the sheet.

Are those any special fields by any chance? As long as you are using system fields and date/datetime custom fields, it should work just fine. If the fields are some 3rd party plugin custom field types, then that might be a problem in the plugin itself.

Have you tried to open the sheet and explicitly change the format back and forth? Maybe that Excel keeps different formats in the background that look the same, but in fact are not. Maybe refreshing them will do the trick - it certainly won't hurt.

Moez SAID

Hello Radek Dostál,

Thanks for your quick feedback and support!

This problem occurs with issue fields and custom fields (I don't have any date fields provided by a plugin)

I applied your suggestion as follows

I tried to modify explicitly the dates in the csv file
1st test:
I explicitly put "25/Apr/19" in the created, updated, resolved and Due date fields

Created	Updated	Resolved	Due Date
25/Apr/19	25/Apr/19	25/Apr/19	25/Apr/19

-->The dates are imported correctly

2nd test
I modify in the same file the same cells "Apr" by "May

Created	Updated	Resolved	Due Date
25/May/19	25/May/19	25/May/19	25/May/19

Note that, in the mapping phase of the field values I checked that the values are correctly interpreted with the desired format
But when importing I get the following message

Import completed with 3 warnings:

Unable to parse created date: 25/May/19
Unable to parse datetime: 25/May/19
Unable to parse date: 25/May/19

In the imported ticket these fields take the operation date ((import date) as values

Jira v8.13.17

Thanks again!

With best regards.

Radek Dostál

Would it be possible for you to send me the sheet data so I can try to import it locally? Of course - not the full sheet, maybe just those 2 rows, one that works, one that doesn't, no extra data or summaries needed, just the dates, I'll fill in the blanks.

I could create it, but I suspect there's something in that sheet.. from what you're saying it sounds that it should work, I did a good amount of date imports in my days but never had a problem with specific months, it was always a cell format.

Generally I just select the whole column minus header and right-click to specify the format for all Date fields, save, and then re-use that format in the mapping. So I don't know, sounds odd, just want to try it for myself if I can reproduce it with your data - might as well spin up 8.13.17 to get the same version.

Moez SAID

Hi Radek Dostál,

I don't know how to join the files (only phots accepted). But if you want to reproduce the problem, you can try an import of a simple ticket with data of type dates on the formats, the months and the JIRA version in question.
For the formatting I use a macro to put in unique format dates because the export file contains different formats of dates on the same column. Something that is already weird sur JIRA
The capture below corresponds to an export csv current fields

Thanks!

Best regards

Drew Kerrigan_4tg868

I've seen the import work with any datetime format using the SimpleDateFormat: https://docs.oracle.com/javase/1.5.0/docs/api/java/text/SimpleDateFormat.html

However it always says:

"...completed with warnings..."

"Unable to parse datetime..."

The only datetime format that I have seen it accept and not throw any errors with, is this:

M/d/yyyy H:mm:ss

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server