Combine quick filters as an OR vs AND statement?

[scott.gray]

Hi Folks,

That title is a bit confusing, I know. but we're looking to see if there is a way to setup quickfilters so they are treated as OR statements instead of AND. eg- if I select quickfilters that are 'assignee was Person X' and another that is 'assignee was Person Y', we'd like to see cards that were assigned to EITHER Person X OR Person Y instead of only cards that were assigned to BOTH resources. Is this possible somehow?

~Scott

[Filipi Lima]

FYI, there's an open feature request for this. It had an odd name and it was hard to find to I updated the name and description a bit.

Ability to configure quick filters to function as OR searches instead of AND searches - JSWSERVER-20741 

[Curtis Fox]

For those using Atlassian Cloud: [JRACLOUD-69062] As a user, I want to be able to choose between an AND keyword or OR keyword when more than one quick filter option is selected.

[Nic Brough -Adaptavist-]

The quick filters work as an AND because they're only useful for drilling down if they work together.

Your need is easy to meet though - create a quick filter with JQL that says "assignee was Person X or assignee was Person Y"

[David Merrill]

90% of the time it is better to have quick filters be OR instead of AND.

Almost every quick filter I have seen within the same board was to select one value of a field (usually assignee).  On my team's kanban board we have ten team members, each of which have a quick filter.  Then we have a quick filters for "unassigned", "Only My Issues" (which is redundant because you can just select your own filter), and "Recently Updated".

Of all of those, only "Recently Updated" should be AND'ed.  All the rest should be OR'ed.

IMO each quick filter should have an operator field to say whether it should be AND or OR.

[Nic Brough -Adaptavist-]

No, it's not.  The quick filters are for drilling down into a board, de-cluttering it of the items you are not interested in.

99% of the time, you would want to do that with an AND, not an OR.

I'm with you on that flag for AND/OR toggling, defaulted to AND of course, to support what the filters are for.  It would be an extra function that would expand the usefulness of quick filters into areas other than drilling down.

[Faruk USLU]

@Nic Brough -Adaptavist-  I do not understand how you can know someone else's daily work. 

As you community leader you should  improve your collaborative skills.

[Nic Brough -Adaptavist-]

Because I've been working with loads of people who use this type of software for over two decades.

[Ru Ch]

@Nic Brough -Adaptavist- even if I take your arguments as valid for every "agile" team setup. (and there can be many you cant know all... stop thinking you know best)

For example the number one usecase in almost every team uses is to quickly filter by User for a daily standup for example. Always having to select user 1 then deselect user 1 and select user 2 it just takes a lot of time and the UI is not particularly fast to react this is just bad design even with an AND relationship. 

I would agree with:

@David Merrill that each quickfilter on its own should decide with a "TOGGLE" if it is a AND or an OR concatenated filter. Additionally I would even go as far as to say that each filter should even get a "STANDALONE" option so that if you select it it deselects all other filters...

Think about what your community wants and not what makes sense to you... that is one of the reasons why Atlassian is loosing its user bases / not getting new smaller companies onboarded.

Leaving only the big companies who cant go away from it at least for now....

Innovation should be done: https://jira.atlassian.com/browse/JSWSERVER-20741

[Nic Brough -Adaptavist-]

And/Or won't solve that problem, so I'm not sure why you mention it here.

I am thinking about what my community wants, did you read any of the earlier conversations?

[Daniel de Vries]

You don't speak for me, @Nic Brough -Adaptavist-. I would be very much helped by such a feature. More so because Assignees and Labels are currently configured as OR filters by default, and Components vice versa, while this isn't made abundantly clear. 

As a community leader, it concerns me that you seem unaware of your blind spots. "Because I've been working with loads of people who use this type of software for over two decades." That's a nice convenience sample to ruminate on, but is it really representative of the global Jira user base?

What would you think if a community member came to you with that kind of rhetoric? I sincerely hope you'd chortle, too.

[Colin Minihan]

When multiple quick filters focus in on urgent items, having the AND is very useful.

[mark scalabrin]

People are coming to this thread because they have a common use case and  @Nic Brough -Adaptavist- is like "no you don't"

Honestly, they should add an or toggle or something.  Yes, sometimes I want to see what multiple people are working on together, sometimes I have two components I would like to combine to see together.  

The list goes on.  

[Jonas Bang Christensen]

I would very much like to have an AND/OR operator option as suggested by @David Merrill. I came to this thread searching exactly for that.

[Henry Chad Apale]

Please add the AND/OR Operator for Static Filters, this is a basic and very helpful ask! :)

[Mark Segall]

Hi @scott.gray and welcome to the community!

Unfortunately, this is not possible natively.  The best alternatives would be either creating a filter or dashboard.

[Faruk USLU]

Hi @Mark Segall ,

Let's say we have several quick filters in a board, and we want to be able to click 2 filters at the same time but see and "OR" functionality instead of "AND" only.

* One solution would be to select an "OR" option when the quick filter is being created
* Another solution would be to put an option on the board to combine "quick filters" by "OR" statement

Do you think it would be  a big hassle to implement such a thing?

[Peter Miss]

Actually there is a way to obtain the result you want, but it's unpractical if you have many choices (people). That is to write the filters to EXCLUDE instead of include for example a person.

So instead of a "John: Assignee = John" filter create a "Hide John: Assignee != John" filter.
This way you HIDE the people you don't want to see and by hiding or not hiding you can combine any people you like. 

[Dawid Kabacinski]

that is the way of thinking!

it works for me. 
My need is to show other team members who is working with whom. We have lots of tasks where two people are working in parallel, so it is helpful to see all current tasks at once. 

And I can not understand how someone can be the opinion "I know everything"!?!?

[Peter Miss]

Nice I could help. I’m new here and a bit confused that even this ”proffesional” forum seem to be more about fighting than trying to help…

[Aaron McMillin]

Sounds like you actually want a multi-select combo box filter :)