When an admin of a team managed project creates a new workflow status for their project's workflow, this status is made available to anyone doing a JQL "status = " search, even if the filtering user has no access to that team managed project. Is there a way to limit the available options for JQL filters so that team managed statuses only show to those with access to those statuses? This is causing a lot of confusion as these statuses can be all over the place.
Anyone seen this? If there isn't a way to prevent this, does anyone have any suggestions for handling this situation?
I suspect the answer is, "no". JQL is not a SQL, and so customers do not get the scoping limits/help you note when using advanced searches. I believe that when using the basic search option, when you first filter by project that the values shown for status are constrained to the selected project.
It does seem like a bigger problem now with Team-Managed projects, as each one adds new status values and custom fields. The suggested "work-around" I saw from the support team is to use the numeric ID value for the status (rather than the name) to make them unique in your query.
There are marketplace addons (for purchase) which improve JQL, making these more unique for searches, but I haven't used any recently which I could recommend.
Jira is a powerful tool that helps teams to plan, manage, and report on their work. We love using Jira, especially for its ability to track issue progress. But how to monitor the...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events