-
Bug
-
Resolution: Not a bug
-
Low
-
None
-
9.12.1, 9.12.5, 9.15.1
-
None
-
9.12
-
1
-
Severity 2 - Major
-
Issue Summary
This is reproducible on Data Center: (yes)
When setting the java date /date.time pickers (Jira Administration>General configuration>Advanced settings) to show year as yyyy, customfields of the type date / timedate picker are setting the year as 0024 even when using the Date Picker
Steps to Reproduce
- Add a Date / TimeDate Picker field to Jira and make sure to add it to some screens
- Navigate to Jira Administration>General configuration>Advanced settings, and set the java date picker / date time picker to format the year as yyyy
- Optionally, set year to yyyy in Jira's Look and Feel - this has no effect.
- Create an issue, and select a Date using the Date Picker!image-2024-04-24-17-39-25-008.png|width=303,height=157!
- Click 'confirm' in the picker (even if Look and feel is set for yyyy you will see
- Proceed to create the issue - see the date is noted on the issue (if Look and Feel is set to yyyy you will see the year already as 0024):
- If the Look and feel is still set to yy, one will only see this issue if trying to update the field inline:
Expected Results
Date is set per the Date / DateTime picker, with the correct year - 2024
Actual Results
The year shows, and saved into the DB is 0024, may not show on the issue view (if Look and feel is set to dd/MMM/yy), but will later fail in JQL search, as it falls way in the past
Workaround
Do not use the date picker, but manually type the full date /time and indicate the year in 4 digits - see also this comment bellow.
- is related to
-
JSDSERVER-8492 IQL Date function to search for objects with a past date returns date in future with year range 2042 to 9999
- Gathering Impact