Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
None
Description
Issue Summary
Attempting to search for issues using the JQL updatedDate >= '2019-03-10 02:56' produces an error indicating the date format is invalid. Changing the date or time to anything outside of 2019-03-10 02:00 through 2019-03-10 02:59 successfully returns results.
Steps to Reproduce
- Ensure that Server timezone is set to Europe/Paris
- Perform an advanced search using this JQL in a Jira Cloud site: updatedDate >= '2024-03-31 02:56'
Expected Results
The search parses the date successfully and returns results.
Actual Results
An error is returned indicating the date format isn't valid even though it is.
Date value '2024-03-31 02:56' for field 'updatedDate' is invalid. Valid formats include: 'yyyy/MM/dd HH:mm', 'yyyy-MM-dd HH:mm', 'yyyy/MM/dd', 'yyyy-MM-dd', or a period format e.g. '-5d', '4w 2d'.
01:59 on that date works:
03:00 on that date also works:
Anything in the 02:XX hour on that specific date fails to parse.
The following messages are shown in the Jira logs:
2024-04-01 12:57:55,386+0000 http-nio-8080-exec-3 INFO admin 777x160x1 1as798m 172.29.213.172,172.50.0.2 /secure/QueryComponent!Jql.jspa [c.a.j.i.s.searchers.transformer.DateSearchInputTransformer] Unable to parse date '2024-03-31 02:50'
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available.
Attachments
Issue Links
- is related to
-
JRACLOUD-74435 Issue navigator fails to parse specific date time
- Closed