Details
-
Bug
-
Resolution: Fixed
-
High
-
85
-
Severity 2 - Major
-
152
-
Description
Hi everyone,
Thank you for your votes, comments, and patience on this issue. Our team has recently investigated this bug. Firstly, we were able to find out why the “status was” queries for company-managed projects are broken in certain scenarios. We are glad to announce that this part has now been fixed: https://jira.atlassian.com/browse/JRACLOUD-79741
We hope that it will improve your experience with JQL and will ease the transition for everyone migrating to Cloud from Server and Data Center.
We understand that many of you require this feature to work with the team-managed (next-gen) projects. We plan to solve the underlying problem but in order to ensure good performance of the search we need to first deliver some necessary architectural improvements. For now you can try using the workaround and replacing status name with status ID for each project as explained in this article.
We will post an update there when new information is available.
Best,
Mila Szydlowska
Summary
For team 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 with team-managed projects
In both scenarios, using the status_id instead of the status_name works. This also affects searches performed via the Jira APIs.
Workaround
Use the Status Id instead of Status name when using was or changed in JQL as explained in this article: https://confluence.atlassian.com/jirakb/in-a-team-managed-project-jql-is-not-working-if-it-contains-status-was-statusname-1163769987.html
Attachments
Issue Links
- is cloned from
-
-
- Gathering Impact
-
- is duplicated by
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Gathering Impact
-
- is related to
-
-
- Long Term Backlog
-
- was cloned as
-
-
- Closed
-
- causes
-
JST-738922 Loading...
-
- is action for
-
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Wiki Page
-