-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
5.3.0
-
None
-
4
-
Severity 3 - Minor
-
0
-
Issue Summary
This is reproducible on Data Center: yes
Steps to Reproduce
- Navigate to any object type with date attribute or add a date attribute to an object type
- Enter a value for the date to be in the future past year 2030 eg. 2037-10-28
- Note the date field accepts only 2 digits for year
- Enter at least one digit using the keyboard
Expected Results
The date is recognized as 2037-10-28
Actual Results
The object is created with the value for that date being: 1937-10-10
This will make all the AQL queries based on the date fail. See: https://jira.atlassian.com/browse/JSDSERVER-11990
https://jira.atlassian.com/browse/JSDSERVER-8492
https://jira.atlassian.com/browse/JSDSERVER-11030
Workaround
Set the date format in Jira to use YYYY for the year, see https://confluence.atlassian.com/adminjiraserver/configuring-the-look-and-feel-of-your-jira-applications-938846975.html
Put 4-digit year in the field e.g. 01/Jan/2050
OR
Use the date picker to select the desired date with a mouse click.
OR
Use REST API to create objects with dates in the future -https://insight-javadoc.riada.io/assets-rest/#object_create_post-
- causes
-
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
-
JSDSERVER-11030 date field Import from LDAP subtracts 100 years
- Gathering Impact
-
JSDSERVER-11990 Insight IQL functions related to date comparison returns incorrect results for dates over 2044.
- Gathering Impact