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; } } }

Possible to add a Component filter to the Kanban board?

Jason Glover_ron1m1

If there was a way to have Component be a filter on the Kanban board I wouldn't need to maintain one kanban board for each one.

One work-around might be to create Quick Filters, but then I have to create one filter for every combination of components I want to filter by. Sometimes I want to see a combination of 3 or 4 or 5 components.

Another work-around would be to use swimlanes, but I'm already using swimlanes for Priority.

component drop down.png

Accepted answers

All comments

Trudy P Claspill

Hello @Jason Glover

Welcome to the Atlassian community.

The presences of those filter pull-downs is managed automatically by Jira, based on there being values on which to filter.

It does not appear that they have included Components as one of those automatically available filters, and there is no way for us to add it in.

I was looking for, but have not yet found, a change request for this in their public backlog.

https://jira.atlassian.com/secure/Dashboard.jspa

Steven White_rq6bxm

Sorry, can you expand on that? How does it decide what fields to include?

I'm having the same issue. I've created a new board, and it's giving the following fields as drop-downs, but I need Components on there, as I already have a number of quickfilters for other things.

Epic
Label
Type
Quickfilters

Trudy P Claspill

Hello @Steven White

Welcome to the Atlassian community.

Review my previous answer:

It does not appear that they have included Components as one of those automatically available filters, and there is no way for us to add it in.

You would have to make individual Quick Filters based on JQL for each Component value.

Steven White_rq6bxm

I thought that was going to be the answer, but was hoping to avoid the need for that as the team already have a large number of quick filters and was trying to slim them down

oh well

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud