Dealing with the known date bug issue in Jira (see below) and have some questions about the fix...

[PR23]

We are encountering issues with dates which is a known bug 

https://jira.atlassian.com/browse/JRASERVER-71354

Using date picker custom field with the format “YYYY/MM/DD”, and setting a date after 2039 using API call, automatically changes the year to 19XX.

In order to fix the problem  we need to update the jira.date.time.picker.java.format under the advanced settings as the system cannot determine if the year is 1940 or 2040. The fix would be to update the date format from d/MMM/yy to d/MMM/yyyy and date time picker from dd/MMM/yy to dd/MMM/yyyy.

My concern is there may be project automation and scripting that relies on the current format and may stop functioning properly.

Is this going to be an issue or is it safe to go and change the date format?

[Tuncay Senturk]

Hi @PR23 

I don't know if you had any answers to your question but here is my two cents on this. Changing the date format in Jira from d/MMM/yy to d/MMM/yyyy will resolve the issue related to dates beyond 2039. However, as you've mentioned, any existing scripts, project automation rules, or third-party integrations that depend on the current yy format could be impacted by this change.