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

First Kanban-Project: Cannot see the Stories

kevin.heusinger

Hey, I worked a lot with Scrum-Projects. But starting a Kanban-Board and creating some Stories leads me to a situation, where I have the board open and see no stories. It says, that I have no stories yet and wants me to either create one or check my board preferences.

I have stories for this projekt created. And in the board preferences I see nothing wrong. The project filter shows all created stories perfectly.

Why is that?

Accepted answers

All comments

Nic Brough -Adaptavist-

We probably need to see the configuration of your Kanban board - specifically the filter and sub-filter for it from the general configuration, and then the column mapping bit.

On the column mapping, we would be checking that you have all valid status mapped into columns so that issues will not be hidden.

The filters are a bit more complex, and I am guessing that, as you've come from Scrum projects, you have not adjusted the way you use versions. Scrum boards use a single board filter to decide what issues to look at, and Kanban does exactly the same.

But Kanban boards have a secondary filter that tells the board how to decide what issues to ignore when they are "done", and the default for that is "set to a version that has been released (or archived)".

So I'm thinking maybe your issues have fix versions that have been released?

Jack Brickey

What type of project are you working with? If this is a company managed project then you should be able to edit the board settings by clicking on the… In the upper right. What's their click on the General tab and inspect your board filter. The filter is what defines what will be seen on your kanban board. Please share what you currently have so that I might help you further if needed.

kevin.heusinger

You are right! The subfilter is configured as "fixVersion in unreleasedVersions() OR fixVersion is EMPTY" - what is the reason for that? why is that the default?

hm. Why are is the fixVersion of my stories not empty by default?

kevin.heusinger

The "fixVersion" must therefore be a released version. But how can that be the default value of the stories I create?

Nic Brough -Adaptavist-

Kanban needs a way to say "this issue is done and no longer needs to be shown on the board".

The default for Jira is to assume that an issue that is in a version that has been released is done and can be dropped off the board. That's why it has a "release" button at the top of the done column which tags all the done issues with a version which it then releases.

But you can change that filter to something else.

If you are going to do Kanban, you should really stop using fix version. It's different to scrum.

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