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 do I make issues visible on a Kanban board?

Bridgette Wilso

I have one Project set up. In this one project, I have two boards (one board for each team). One team does development work and will use a scrum board and one team does maintenance and that will use a Kanban board. How do I make issues for the maintenance team visible on the Kanban board? Right now, when I create an issue, it shows up in the backlog of scrum board for the development team.

Accepted answers

All comments

Jobin Kuruvilla [Adaptavist]

You can configure the filters of both the boards to show only the appropriate issues in each board. In your case, check the filter query of the Kanban board to see if it filters out that issue.

Svante Gustafsson Björkegren

Hi Bridgette,

It is all about the filters you apply to the two boards.

E.g. if the teams are using different issue types you can create the filters to catch the correct issue types for each board.

If they are using the same issue type you will need some other way to distinguish the tickets. maybe a custom field showing if it is a maintenance ticket or a development ticket.

This page describes how filters work: https://confluence.atlassian.com/display/JIRA/Using+FiltersThe filter used by each board is found under the board config.

Also check out this page: https://confluence.atlassian.com/display/AGILE/Configuring+a+BoardIt describes well how to configure your boards.

Cheers,

// Svante

Bridgette Wilso

Each team will use the same issue type, so I thought I would use labels to distinguish the tickets. But, when I click on the Quick Filter that I set up, the query is not picking up on the label. Is there a better way?

Ted Tencza_rs4l8u

Labels are case-sensitive. Double check that your filter query and labels match case.

Bridgette Wilso

Hi Ted! Thanks! I checked the case. It matches. Unfortunately, my issues are still hidden on my kanban board. I can see that I have two issues when I configure my board, but when I view my board the issues are hidden. Do you have any other suggestions of what I can check to see why my issues are hidden?

Svante Gustafsson Björkegren

Hi Bridgette,

If your issues show up in the issue navigator when using the same filter there are three things that could potentially hide them in the board:

Quick filter - make sure you have no enabled quick filters in the board
Column configuration - If there are unmapped workflow steps in your board. This does not seem to be the problem in your case, so ...
The Board Sub-filter is hiding the issues. The subfilter (found at the bottom of the Board/Configuration) is an extra filter that you can apply within the board. It is normally used to hide issues that are released to a FixVersion. It looks something like "fixversion in unreleasedversion() OR fixversion is EMPTY" If you have issues beloning to a released fixversion they will be eclipsed by this default sub-filter. Try to remove the sub-filter and see if your issues re-appear.

If that is the case and you don't work with the release functionality in JIRA you can leave the sub-filter empty. You can read more about this here: https://confluence.atlassian.com/x/jYRPFw

Cheers,

// Svante

rossmcf

Oof.

I had the same issue. The subfilter solved it, but that is a sneaky one!

Joshua Wold4

Thanks this helped me.

Jason Schmitt

subfilter got me too. cool feature but very sneaky.

d4vidi

Here's a nasty end-case I've recently solved:

I have a Kanban board attached to a filter whose query includes specific labels.

I've set my board's swimlanes to be based on Epic, and wound up with nothing but the default "Issues without epics" swimlane.

As it had turned out, issues having suitable labels didn't show in case their associated Epics didn't have the labels as well. I added the proper label to Epics - expected issues started showing on the board.

Nic Brough -Adaptavist-

That's not a "nasty" end-case. You just got your filter wrong.

d4vidi

I beg to differ! The filter worked perfectly - all issues were available as part of the query result as expected; Nevertheless, they just didn't show on the board simply because the epics didn't have the label. This coupling isn't trivial.

Nic Brough -Adaptavist-

That's simply not how it works. What you have described is an incorrect filter hiding things.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-software