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

kanban board

Leila Schollar

I am very new to Jira and am working on my first Kanban Board for a group that have already started before me. They have asked me for the below, any advice would be appreciated.

Components to be put up on the board that run concurrently and do not change: for billing purposes, authentication. On the board that they have created I cannot find the components at all. I did some googling and found out that there are different types of Kanban Boards (I'm not sure that is the right word) which means I would have to create a new board and import all the issues and current work into that board. My question is whether I am right or have I missed something. If I am right, what could I use instead of Components as I don't think Epics would serve the purpose they want to use it for. Would components even be the right feature to use?
I would also like to add a backlog lane to the swim lanes that they have and not display it on the board-is this possible? At the moment they have selected for development, blocked, in progress, review and test, done. They have asked for a backlog swim lane that won't be displayed on the board.

Accepted answers

Jack Brickey

Hi @Leila Schollar . So I’m unclear exactly what you want to do with components. However components is a default field in all Jira projects. Are you wanting to display the component for every issue on the cards in your kanban board? Or maybe you wish to have swim lanes by component?

Nic Brough -Adaptavist-

Ok, there's a few things in here:

An important thing to understand is that a board is not a container for issues, it is a view of a selection. I know you've not mentioned anything about this in the question, but I always find it's worth re-stating when people are new to boards.

>Components to be put up on the board that run concurrently and do not change:

"Components" in Jira is a Jira-speak reserved word - there is a system field called components that is a project concept and it is usually used for breaking up projects, or rather, grouping things in a project. Really bad analogy, but if you were using Jira issues to track "pets", you might have components representing "colours", so with a list of options like blue, grey, ginger, black, white, lilac. PET-1, PET-2, PET-3 in our house all used to have the single component of "black" before they died, but PET-4 has components of white, ginger and black, and PET-5 grey, ginger, white, black and lilac.

These values are issue values, not things that directly appear on a board outside the issues. You can of course, use them for filtering (quick filters or swimlanes, or even for the board itself)

But for your overarching billing/auth/development etc, yes, you may find Epics are a far more natural and easy way to see things grouped on the board. A lot of people run boards with never-ending epics for exactly that reason

>are different types of Kanban Boards

Almost - it's not so much that there are different types of Kanban board, but the Kanban boards function differently depending on where they are defined, and they have a lot of flexibility, so you might well see two Kanban boards that (for ease of explaination) are of the same "type" but work very differently.

Broadly, you'll see four "types" of things that look like Kanban boards:

Kanban boards from team-managed projects - these will look similar to each other, they're tied to a project and don't have a huge amount of flexibility
Business boards in Jira Core projects - these are also tied to a project and have almost zero configuration. They look a bit Kanban-y but really are not Kanban boards
Scrum boards that have been configured to be very close to Kanban boards (I'll ignore these, you could argue that they are all very close to cases 1, 2 or 4 anyway)
Kanban boards that handle company-managed projects

The 4th is the most important here - they are based on filters more complex than just "the project", you can build all sorts of cross-project, ignore other stuff lists of issues for your board, and have multiple boards all doing different things with the same issues.

>I would also like to add a backlog lane to the swim lanes that they have and not display it on the board-is this possible? At the moment they have selected for development, blocked, in progress, review and test, done.

I think you are mixing up Columns with Swimlanes here. A column contains one or more status and the idea is that as an issue progresses, it will move from one column to the next, eventually landing in the last "done" column.

A swimlane goes across the board, grouping issues into layers.

I think what you mean is you want that issues in the backlog do not show on the board. Depending on the type of board you're using, this is possible, check the backlog and board settings (a company managed project for example, you could not map the status from the backlog. team-managed let you do it with config flags)

All comments

Jack Brickey

Leila Schollar

Hi @Jack Brickey

Thank you for responding. Why can't I see the Components field in my Kanban Boards?

I want to be able to have something that can run independently of Sprints.

Nic Brough -Adaptavist-

Ok, there's a few things in here:

>Components to be put up on the board that run concurrently and do not change:

These values are issue values, not things that directly appear on a board outside the issues. You can of course, use them for filtering (quick filters or swimlanes, or even for the board itself)

Broadly, you'll see four "types" of things that look like Kanban boards:

Kanban boards from team-managed projects - these will look similar to each other, they're tied to a project and don't have a huge amount of flexibility
Business boards in Jira Core projects - these are also tied to a project and have almost zero configuration. They look a bit Kanban-y but really are not Kanban boards
Scrum boards that have been configured to be very close to Kanban boards (I'll ignore these, you could argue that they are all very close to cases 1, 2 or 4 anyway)
Kanban boards that handle company-managed projects

A swimlane goes across the board, grouping issues into layers.

Leila Schollar

For example, we want to be able to include billing/invoicing for work done on the kanban board.

Jack Brickey

be sure to consume Nic’s valuable input.

then…

If you wish to display Components on each card….

click on the ellipses in upper right
select board settings
select card layout
Select Components in the drop down and click add

if you wish to display swimlanes (horizontal lanes) you will have to use swimlane by queries…

click on the ellipses in upper right
select board settings
select swimlanes
select queries in the dropdown
enter each component into a query, e.g. Components = accounting, Components = development, etc. for each component

Leila Schollar

Many thanks for understanding and explanation!

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud