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 based on Stories

Bayar Said

Hello, I am trying to figure out how I can set my kanban board based on my each stories i created.

I have already tried to set it on stories using the option jira already set up:

stories swimlane base.jpg

However its not working how I actually want it to be.. If I set the swimlanes based on Storys via the option mentioned above, the result coming out is based on Tasks and showing Sub-Tasks i created for those..

Thats how i created my WBS:

And that is how I want my Kanban Board look like:

I have already tried using JQL but couldnt figure it out yet.. I hope someone could help me out!

Thanks in advance!

Accepted answers

All comments

Craig Nodwell_7eve9b

Hi @Bayar Said when you base your swimlanes on Stories the Story becomes the swimlane and it's children become the cards on the board in that lane. This is how the board is designed. What are you looking for in the board that you are not getting, maybe provide a screen shot of that.

Bayar Said

Hi @Craig Nodwell this is the result i get when i set the swimlanes based on Stories using the option:

screen result.jpg stories swimlane base.jpg

Craig Nodwell_7eve9b

Yes, that's working as designed. The story itself is the swim-lane, it's children cards display below.

Bayar Said

No, the swimlane itself is based on Task 1.2 and showing me only the sub-tasks of Task 1.2.

Task 1.1, Story and its tasks of my second epic are missing totally..

What I want are swimlanes for each Stories, like this:

Alex Ortiz

I see the problem here. You can't do what you are trying to do in Jira. You are trying to make a Task be the child of a Story. And the Sub-task be the child of the Sub-task. Jira doesn't work like that.

You have to treat your Story and your Tasks as the SAME level. That means that a Story can ONLY have a sub-task as a child. The same for a Task, it can only have a Sub-task as a child. Story and Tasks are siblings. . . .at the same hierarchy level.

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

kanban