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.
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.
Hi Everyone! My name is Mina and I am on Atlassian’s Ecosystems Marketing team. Our team is focused on our technology partnerships and marketplace apps. One of Atlassian’s partners is Slack, who ...
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