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 backlog not working

Mark Coleman

Hello! I have a project in progress that has been run as a Scrum project with Sprints. We are transitioning to a Kanban approach instead. I have a new Kanban board setup. I have added the Kanban Backlog column to the board and assigned the status of "To Do". When I view the board, the backlog column does not show up. If I go to the Backlog nav item on the left, I can see a set of stories in progress and a long list of stories in the backlog section, all with the status of To Do.

What can I try?

Thanks so much!

Accepted answers

Jack Brickey

with Kanban the Backlog column will not show on the Kanban board. It basically moves the "To Do" to the Backlog board for planning purposes similar to Scrum. You move items from backlog to selected for development and then when moved to in progress they disappear from the backlog and are solely shown on the kanban.

All comments

Jack Brickey

Mark Coleman

Thank you for the super quick reply!

Our project has a "custom workflow" with To Do, In Progress. In QE. etc.

Will our workflow work ok with the Kanban board? You mentioned moving items from backlog to selected for development. I'm assuming selected for development is a standard Kanban stage. Is this stage a column on the board? I'm trying to follow you on the last part of your reply about moving from the backlog to selected for development and then to in progress.

My backlog area has a section for backlog and a section for in progress.

Jack Brickey

Certainly. Question for you - when you created the kanban and moved the To Do into backlog and navigate to the Backlog board what do you see at the top? There should be two 'sections': Selected for development (or similar) at the top and Backlog at the bottom.

oops... i just saw your last sentence. In Progress equates to Selected for development in your case. The difference is that in your case issues will remain on your backlog board in the in progress status until they transition to the next status. I like the Select for Dev as it clearly defines work to be done from work 'being' done. Not a biggie.

Mark Coleman

I understand! Thanks! This gives me a lot to work with.

Welcome!

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

Quick Links

Find more posts tagged with

jira-software