-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
10.3.5, 10.6.0
-
10.03
-
2
-
Severity 3 - Minor
-
4
-
Issue Summary
Calendar date picker does not account for leading digits of year when editing a due date on an issue.
For example if a user accidentally enters 05/12/0023 as the due date on an issue the value stored in the database will be: 0023-05-12 00:00:00.000 +0000. However, when selecting to edit the due date on the issue view May 0f 2023 is rendered:
- Adjusted date format in Jira Administration > System > User Interface > Look and feel > Day/Month/Year Format to dd/MM/yyyy to demonstrate the issue more clearly.
Steps to Reproduce
- Create an issue in a Jira project that has Due Date configured.
- Ensure that the due date is on the edit screen for the project/issue type in question.
- Add a due date value via the Edit screen. The field help identifies the format to be (d/MMM/yy) which is a typo but dd/mm/yyyy is able to be entered here. For the sake of testing enter in 05/12/0024 and Update the issue.
- From the issue view select to edit the due date and select the Calendar icon. This will cause a calendar date picker to appear where the selected date will be May 12th of 2024 instead of May 12th of 0024.
Expected Results
Date picker should auto populate based on value stored in database.
Actual Results
Date picker assumes year of date value to be 20**
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- relates to
-
JRASERVER-31291 2-digit year on Jira Date Picker converted to 1900 if 20 years or more in the future
-
- In Progress
-
-
JRASERVER-78093 In a Date Picker field, if year is wrongly typed starting with "00", the date will be saved as 2 days earlier
-
- Gathering Impact
-