Wrong dates trough CSV import

[Robin Weiß]

Hi,

I imported a few stories with a due date via a CVS import. Most of the issues have the right due date but the system changed 2018-12-31 to 31/Jan/18 while 2019-01-01 is still 01/Jan/19. 

Is here someone who knows the source of this problem or knows a way to avoid it for future imports?

Thanks a lot!

[Andy Heinzer · Accepted solution]

I'm not certain of the problem here.  But at least from the way you describe the issue, I'm curious to learn more about your environment.   Is it possible that your Jira installation has modified the jira.date.picker.java.format and/or the jira.date.time.picker.java.format under advanced settings?

If so, then I can see a scenario where Jira could be processing your date records in a way that it believes is correct, but actually is causing inaccuracies.   If you have modified theses, could you please share with us the specific modifications you have for all these settings on that page:

jira.date.picker.java.format
jira.date.picker.javascript.format
jira.date.time.picker.java.format
jira.date.time.picker.javascript.format

[Robin Weiß]

In the screenshot you'll find our settings of the date format. I can't remember of a change in these settings.

In the CSV uploade I've chosen yyyy-mm-dd.

[Andy Heinzer]

Those system settings looks to be the defaults, so I don't think there is the problem as far as I can see now.

When you are doing this CSV import, Are you using the External System import?  (Gear icon -> System -> External System import -> CSV)

If so, then you should see in the setup a date format option again,

You mentioned you are using a format here of

yyyy-mm-dd

Please note that for the month field 'm' != 'M'.   The lower case m is meant to display the minutes in the hour.  While the upper case M is the month of the year.  Try this import again and use the date format of

yyyy-MM-dd

Please let me know the results.  I think this should resolve this inconsistency.

Andy