-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
8.20.8, 9.12.13, 9.17.2, 10.0.1
-
8.2
-
4
-
Severity 3 - Minor
-
0
-
Issue Summary
In a Date Picker/Date Time Picker field, either, be it a custom field or any default field like the Sprint Start/End dates field or the Target Start/End fields, if the year is wrongly typed starting with "00", the date will be saved as 2 days earlier from what it was previously.
This is reproducible on Data Center: yes
Steps to Reproduce
Sprint Dates
- Spin up a vanilla Jira
- Create a Scrum project with sample data
- Create a Sprint, with Custom Duration
- Select the Sprint Start and End dates
- Edit the date, adding "00" to the year, as shown below and save
- Edit the Sprint dates again and note the date will display as being 2 days earlier
Custom Field dates
- Spin up a vanilla Jira
- Create a Project Management project with sample data
- Create a Date Picker custom field and add it to the project
- Add a valid date to edit
- Edit the date, manually adding "00" to the year (e.g., change the year from "24" to "0024")
- Save and note the date was changed to 2 days earlier from what it was set previously
Expected Results
Although the year could be wrong, the date should be the same.
Actual Results
The date is saved as 2 days earlier than what it was set previously.
Workaround
Ensure typing the correct year when saving the changes to a date field.
- is related to
-
JRASERVER-78814 Calendar date picker does not account for leading digits of year when editing a due date on an issue.
-
- Long Term Backlog
-