nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How can we use more than filter at once?

Jeff A_1wlp6b

We have a team that wants to have a litany of filters so that they can operate in such a way that they are like search features.

For example, they have several filters as follows:

Bob -- project = PROJECTNAME AND assignee = Bob

Mary -- project = PROJECTNAME AND assignee = Mary

Sue -- project = PROJECTNAME AND assignee = Sue

Kyle -- project = PROJECTNAME AND assignee = Kyle

They also have some filters by Component, Epic, and Issue Type.

Epic 1 -- project = PROJECTNAME AND "Epic Name" = Epic1

Epic 2 -- project = PROJECTNAME AND "Epic Name" = Epic2

Bug -- project = PROJECTNAME AND issuetype = Bug

Task -- project = PROJECTNAME AND issuetype = Task

What they had envisioned was the ability to turn on the Quick Filters for Bob and Bug and see all of the Bug Issues that Bob is working on. Then, then could turn off the Bug filter and turn on the Task and Epic 1 filter to see all of the Tasks in Epic 1 that Bob is working on.

Is that something we can do in JIRA? It seems that if I enable two filters they are cancelling each other out instead of working in tandem.

Accepted answers

Jeff A_1wlp6b

It was because I'm an idiot and was using "Epic Name" instead of "Epic Link" and didn't test with any other filters besides Assignee and Epic Name before thinking I had a problem and posting.

All comments

Rodney Nissen [Work Wranglers] [TJL]

Quick filters are AND'ed to the main query of your board. If you have multiple quick filters , it's like you add each one to the end of your Board filter with an AND. ex: "(Board Filter) AND (Quick Filter 1) AND (Quick Filter 2)" There for it's entirely possible to do what you want.

I find best practice is to keep the Quick Filter JQL as simple as possible In your example, I suggest you have Bob's filter be "assignee=BOB" or "issuetype=Bug". Keep the Project = PROJECTNAME to the board filter, so it's only run once rather than once per subfilter. This will help your board run a bit faster by not having to repeat operations, and may solve your problem.

If that doesn't work, recreate your entire filter - with the board filter and quick filters - in the main. Something like this

(BOARD FILTER) AND (QUICK FILTER)
(Project = TEST) and (Assignee = rnissen)

From there, you should be able to figure out which part isn't happy.

Trudy P Claspill

When you enable multiple Quick Filters the results will be issues that fall within the scope of both filters.

This should work properly when you select the Bob filter and the Task or Bug filter.

Your Epic filters will give you the Epics only, not the child stories of the Epics. Epic Name is a field used only in the Epic issue Type. If you want the child stories of the Epic you need to use "Epic Link = <issue key for Epic>".

Note, though, that the Epic Link field is not used at the Sub-task level, nor on the Epics themselves. So if you enable that filter you will not see the Sub-tasks that belong to the child issues of the Epic, nor the Epic itself.

Jeff A_1wlp6b

It was because I'm an idiot and was using "Epic Name" instead of "Epic Link" and didn't test with any other filters besides Assignee and Epic Name before thinking I had a problem and posting.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server