-
Bug
-
Resolution: Fixed
-
High
-
67
-
Severity 2 - Major
-
125
-
Summary
For company managed projects, when searching for issues using JQL such as:
project = PROJECT_NAME AND (status CHANGED FROM "To Do" OR status = "To Do")
status was "In Progress" after "2022-03-09" AND status in ("Ready for Release", Done, Closed, Declined, Postponed)
status was "In Progress" after endOfDay(-21d) AND status in ("Ready for Release", Done, Closed, Declined, Postponed)
assignee WAS currentUser() AFTER "2022-01-01" AND project = "DEMO"
If JQL contains "WAS" and AFTER or endOfDay it ** does not consider the timeline and returns all results.
The results are unreliable.
Steps to Reproduce
- Work case 1
- Create a project with statuses "To Do", "In Progress" and "Done".
- Create some issues, and transition some of them around.
- Run the query: project = PROJECT_NAME AND (status CHANGED FROM "To Do" OR status = "To Do")
- Run the query status was "In Progress" after endOfDay(-2d)
- Work case 2
- Have or create several issues in and outside of the required parameters
- Run the query status was "In Progress" after endOfDay(-21d) AND status in ("Ready for Release", Done, Closed, Declined, Postponed)
Expected Results
- Only issues in the specified parameters should be returned.
Actual Results
- Issues not in the specified parameters are returned
Notes
We primarily see this happening in these scenarios:
- The search doesn't work well in company-managed projects when there has been a workflow change
- is cloned from
-
JRACLOUD-78540 JQL query search using "status was" returns incorrect unreliable results for Team Managed projects
- Closed