Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Is it possible to prevent team managed workflow statuses from showing to all in JQL?

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?

1 answer

1 accepted

0 votes
Answer accepted

Hi @Michael Stewart 

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.

Best regards,

Bill

Unfortunately more of our users use Advanced searching.  And Quick filters require JQL as well, so that's moot anyway. 

Thanks for your reply.  I'm surprised this is not an issue for more people.  It really makes it hard to have a mix of Company Managed and Team Managed projects in your environment

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.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Team-managed projects

4 steps to get actual statuses on the Jira board.

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...

1,199 views 10 14
Read article

Community Events

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

Events near you