-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Component/s: Work Item - Search - Backend - JVIS
-
None
-
1
-
Severity 3 - Minor
Issue Summary
JQL query returns invalid date format error for certain time zones
Steps to Reproduce
- Step 1: Create a JQL query using the format "createdDate > 'YYYY/MM/DD H:MM'" (e.g., createdDate > "2023/3/26 3:10")
- Step 2: Test the query with different time zones, specifically those in the "Europe" region (e.g., GMT+1, GMT+2, GMT+3)
the Default user time zone appears to be (GMT+02:00)Bucharest. Please note that this is actually incorrect, because Bucharest is now on GMT+3!!! Not sure if this the cause of the problem, but it might be related. See the picture attached. The time zone of my account (danut.manda@stonikbyte.com) is Europe/Bucharest. If I change the timezone of my account to “Europe / Amsterdam” (GMT+2) this query works now: createdDate > "2023/3/26 3:10" But, this one starts getting the error (Date value '2023/3/26 2:10' for field 'createdDate' is invalid.): createdDate > "2023/3/26 2:10" So yes, the issue is related to the current user's time-zone. The pattern for reproducing the error is the following: If the time-zone is GMT+1, this query will fail: createdDate > "2023/3/26 1:10" If the time-zone is GMT+2, this query will fail: createdDate > "2023/3/26 2:10" If the time-zone is GMT+3, this query will fail: createdDate > "2023/3/26 3:10" … But, this seems to happen only for “Europe*” time zones. If I select “Egypt“ (+0*2*:00) this query works: createdDate > "2023/3/26 2:10 But if I select “Europe/Amsterdam“ (+0*2*:00), the same query fails.
Expected Results
The JQL query should return the correct results without any errors, regardless of the user's time zone.
Actual Results
The JQL query returns an invalid date format error for certain time zones, specifically those in the "Europe" region. The error seems to be related to the current user's time zone and the hour value in the query.
Workaround
Change the timezone to anything other than Europe. But this is not feasible for many users.
- mentioned in
-
Page Loading...