-
Bug
-
Resolution: Fixed
-
High
-
43
-
Minor
-
27
-
Issue Summary
Historical JQL searches that use WAS with DURING or AFTER or ON. Might give inaccurate results. They might return additional issues.
Steps to Reproduce
- run of one following JQLs:
- <field> WAS X DURING (A, B)
- <field> WAS X AFTER A
- <field> WAS X ON A
Expected Results
Correct issues are returned.
Actual Results
In some rare cases, JQL will return additional 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 history of some issues. Only JQL is affected as that data is only used by JQL engine.
Workaround
If you are experiencing the problem described in this ticket please contact Atlassian support so we can assist you in fixing it.
- duplicates
-
JRACLOUD-78540 JQL query search using "status was" returns incorrect unreliable results for Team Managed projects
- Closed
- has action
-
LYNX-1301 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...