Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
2
-
Severity 3 - Minor
-
Description
Issue Summary
Users are allowed to set a Due date any value for any required year in the future. However, if the date is set beyond 20 years, the date is automatically reset to the same day and month, but 100 years ago(resulting the year being in the 19XX).
Steps to Reproduce
- Include the Due date field in the Create issue and Edit issue screens.
- Create an issue/Edit an issue and set the Due date to anything over 20 years from now.
- Refresh the issue and see that the Due date is automatically updated to an year that is 100 years before the year set by you.
Example:
Expected Results
If 20 years is the maximum limit, users should not be allowed to set a date above that limit.
Or
A error/warning message should be displayed related to the year they have chosen.
Actual Results
Jira automatically updates the field value to an ear that is 100 years prior to the year selected.
Workaround
Kindly ensure to choose a year within the next 20 years.
Attachments
Issue Links
- is related to
-
JRACLOUD-65027 Date picker custom field with the format "d/MMM/yy", and setting a date after 2030, automatically change the year to 19XX.
- Closed
-
JRACLOUD-72814 Selecting a date from 2030 and the following years converts the year to 19xx
- Closed
-
JSWCLOUD-25791 Increase maximum range for Date type field
- Gathering Interest