-
Bug
-
Resolution: Timed out
-
Medium
-
7
-
Severity 3 - Minor
-
1
-
Issue Summary
JQL searches with issue status names coupled with some complicated clauses does not work for team-managed project issues.
Steps to Reproduce
- Create a team-managed project with some issues in different statuses
- Perform JQL search for example:
project = "Team managed project" AND status changed from 'To Do' to 'Done'
- Search will fail for team-managed but the same would work as expected for company-managed projects.
Expected Results
Simple issue status names should work for team-managed project issues for any JQL query.
Actual Results
JQL searches fail for Status Changed To and Status Changed From clauses
Workaround
Currently, JQL for team-managed projects in these situations accepts the Status ID of the status you wish to search for but these are unique to the team-managed project they belong to.
Example of a successful query:
project = "Team managed project" AND status changed from 10245 to 10248
where
10245 = 'To Do'
10248 = 'Done'
To find the status ID for your team-managed project, you may use the following API call:
GET /rest/api/3/project/<Insert project key>/statuses
- is duplicated by
-
-
- Closed
-
- relates to
-
-
- Closed
-
[JRACLOUD-78387] JQL - Status name unexpected behavior for team-managed projects
Hi everyone,
Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.
Thank you again for providing valuable feedback to our team!
Jira Cloud team
This defect is a design problem in JQL: by not limiting the scope of the query to the projects referenced the query is apparently ambiguous. It has been made worse by the design choices for team-managed projects (TMP), thus creating extensive work for Jira admins with larger sites, and for non-admin Jira users, who make the mistake of allowing creation of even one TMP.
Please reconsider fixing this issue, or better still, changing JQL to be an actual ISO compliant SQL, which would instantly solve such problems during parsing and plan building of queries. For more information, please discuss with a DBA.
Thank you.