Summary

There is an issue in Jira Date/Time picker customfields when installed/bundled Java (JDK/JRE) environment is impacted with one of the recently know JDK issues JDK-8208487.

This is noticed specifically when the user profile is set to use spanish/german languages, however, not limited to only these languages. When users select a date/time in a date/time picker customfields, system seems to insert a value which is not valid. Users notice below error in the create issue screen and wherever the date/time picker customfields are used.

Problem happens even when Jira is using default date formats configured in Date/Time Global settings for parameters ("jira.date.time.picker.java.format" and "jira.date.time.picker.javascript.format"). 

Invalid date format. Please enter the date in the format "dd/MMM/yy h:mm a".

Formato de fecha no válido. Por favor introduce la fecha con el formato "dd/MMM/yy h:mm a".

Value entered by picker: 17/Jan/22 05:04 PM
Invalid date format. Please enter the date in the format "dd/MMM/yy h:mm a".
System default is:
dd/MMM/yy h:mm a

Value entered by picker: 17/ene/22 05:04 PM
Formato de fecha no válido. Por favor introduce la fecha con el formato "dd/MMM/yy h:mm a".
System default is:
dd/MMM/yy h:mm a

Environment

• Jira Software 8.19.X and JSM 4.19.X and above versions.
• Systems running on JDK9/Bundled JRE and above which are running on CLDR and COMPAT is not enabled. If COMPAT is already enabled the issue is not noticed.

Cause

The problem is specifically noticed if the JDK/JRE in action (installed) is impacted with one of the recently know JDK issues JDK-8208487. 

Problem only happens with Java versions using Common Locale Data Repository (CLDR) enabled. If COMPAT (COMPAT: Represents the locale sensitive services that are compatible with the prior JDK releases up to JDK 8) is enabled for JVM the problem doesn't happen.

Solution

Add the specific JVM argument mentioned below to ensure Java (JDK/JRE) is compatible with locale sensitive services (letters and special characters) that are compatible with the prior JDK releases up to JDK 8. Refer to this article for detailed instructions: Setting properties and options on startup 

-Djava.locale.providers=COMPAT

NOTE: Once the changes are made, ensure to restart the instance for changes to be effective. If you are using Data Center cluster, changes have to be applied on all nodes followed by round robin restart.