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

Stories with no Sub Tasks lose Rank

rishida

Hi, I'm currently using the "Base Swimlanes on Stories" option, but this places all User Stories with no Sub-Tasks at the bottom of the board.

I've tried using JQL to create a filter that would allow filtering by Stories while still keeping Stories without Sub-Tasks in the proper order, but haven't been able to come up with anything that works.

Does anyone have an alternate solution for this?

Thanks!

Accepted answers

All comments

Timothy

but this places all User Stories with no Sub-Tasks at the bottom of the board

They are not at the bottom per-se. It just displays the sub-task with the stories. Ranking is not lost if i'm not mistaken

rishida

Thanks Timothy. Do you know if there is a way to prevent the Stories with Sub-Tasks from being at the bottom?

Tom Haraldsen

Also covered here.

rishida

Thanks Tom. I actually looked at that before posting, but I've tried a JQL filter, and I haven't been able to come up with anything that works. I'm hoping that someone has come across an alternative that I would be able to use.

rishida

Hi, has anyone come up with a JQL solution to this issue, or something similar?

Dave Todaro

I'm also frustrated by this because the team has to refer back to the product backlog to figure out what the correct priority order is.

To keep things simple, we only add sub-tasks to bugs and stories when needed (for example, if the team feels they can get a bug through In Process and Ready for Test in 4 hours, we wouldn't create sub-tasks in that case.)

Here's what we want the task board to look like, where the bugs and stories keep their priority order:

Bug

Sub-task

Story

Sub-task

Story

Sub-task

Story

Is there any way we can do this? We want the best of both worlds...we want sub-tasks to continue to be grouped by bug/story, but we want to keep the priority order from the product backlog.

Thanks!

Dave Todaro

Shoot - my indentation was stripped out. Pretend "sub-tasks" are indented under the bugs and stories, denoting that they're grouped.

Andrea_Guardascione

I guess 6 years later we still have the same error

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