-
Bug
-
Resolution: Fixed
-
Highest
-
43
-
Severity 3 - Minor
-
40
-
Customers that migrated from Server to Cloud recently (After March 2024).
Issue Summary
Customers might experience trouble running historical JQL searches using WAS/WAS IN with BEFORE/AFTER/DURING/ON.
Steps to Reproduce
- Run one of the following example JQLs:
- status WAS closed DURING ('2024-01-01', '2024-01-31')
- assignee WAS currentUser() AFTER/BEFORE startOfYear(-1)
- priority WAS P1 ON '2024-01-01'
Expected Results
Issues within the date range and condition are returned.
Actual Results
In some cases, the historical JQL search will return additional issues or no issues. Issues that had value X set to <field> before A but it has been later (before A) changed.
This is caused by corrupted data in the history of some issues. Only JQL is affected, as that data is only used by the search engine.
Workaround
If you are experiencing the problem described in this ticket please contact Atlassian support so we can assist you in fixing it.
- depends on
-
WASABI-504 Loading...
-
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-