You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
This question is in reference to Atlassian Documentation: Configuring Quick Filters
Currently multiple quick filters impose and AND condition across multiple constraints. Is it possible to change to an OR operator so that you can select multiple different filters that would all justify inclusion.
No, I'm afraid there's no way to do that. It would be nice (although the UI designer I've spoken to about it says it's hard to sensibly show the mode on-screen to avoid "why isn't an and/or" questions from end users)
I agree with Rohan. A simple filter to show label:red and label:yellow is a great example of something that as a PM I would like very much. Also due:30 and due:overdue would be another one. Guy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
One way you could achieve this is by treating checking the filter as EXCLUDING those items.
Then all unchecked things would remain.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Quick Filters are intended for simple cases. For more complex searches, including OR, use the regular JQL Basic or Advanced search for issues
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sometimes you need additive quick filters, so this intention though understandable can always be challenged I think.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just curious about the comment for quick filters being "intended for simple cases" as some of our users are seeing some weird scenarios. What goes beyond simple and causes quick filters to break?
For example, we have quick filter "A" defined as "Custom Select Field" != "XYZ" and quick filter "B" defined as being "component not in (some.component).
When using quick filter "A" or "B" by themselves, they are fine. However, when using them additively / together, the query doesn't work.
Thanks in advance for your input.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.