Details
-
Bug
-
Resolution: Obsolete
-
Low
-
1
-
Severity 3 - Minor
-
Description
Summary
Using date picker custom field with the format "d/MMM/yy", and setting a date after 2030, automatically change the year to 19XX.
Affected Version
JIRA v1000.844.1
JIRA v1000.711.0
Steps to Reproduce
- Create a date picker custom field
- Associate the custom field with the project
- Create a new issue
- Set any date > 01/Jan/2030
Note that the date was changed to 01/Jan/30 (01/01/1930)
Expected Results
Keep the correct date which was set.
Actual Results
It automatically set the wrong year. All the issues with the wrong year are resulting in JQL queries with "date picker custom field" <(now)
Workarounds
- Set a year < 2030. (ie. 31/Dec/29)
- Use a date format for the year of "yyyy"
Attachments
Issue Links
- relates to
-
JRACLOUD-82550 Due date is automatically set back to 100 years ago when choosing any year over 20 years.
- Gathering Impact