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

Order of stories on next-gen board with "group by subtasks" enabled

ulich

I have a next gen project and in the backlog there is the following order of stories for the board

2019-10-14 at 10.30.jpeg

I have the board configured with "group by subtasks".

I would expect the stories on the board to have the same order, but they are completely different.

2019-10-14 at 10.24.jpeg

Can this be changed somehow? For me it is absolutely crucial to have the stories on the board with the priority they should be worked on, from top top bottom.

Accepted answers

Eoin

@ulich this should now be resolved for you - the ordering of swimlanes will respect the rank of the story and will align with your backlog view and issue view. Let me know if you have any further questions!

All comments

Eoin

bwebster

@Eoin I am seeing the same issue that was reported by @ulich in our nextgen project. The issue does not appear to be fixed for our project.

I can compare the backlog with the board when grouped by "none", and they match. I can also compare the backlog with the issues view when filtered to our project and ordered by "Rank" (which seems to look like a custom field). These two views also match up.

When I look at the board grouped by "subtask", the order doesn't match.

Eoin

Thanks for flagging this with us @bwebster - we'll take a look

Jonas Sossai Junior

Hi @Eoin

Same issue hire. Backlog order is this (correct):

And board order is this:

Any idea?

Thanks
Jonas

Andy Heinzer

Hi everyone,

Sorry to hear about this continued problem. This is a bug we are tracking over in JSWCLOUD-17950. I recommend watching that issue for updates on this problem. Please vote on that issue if you are affected by this particular problem. This can help our team to better understand the number of systems affected by this problem so that we can better prioritize the most urgent problems.

Thanks

Andy

Fabio Pulvirenti

The bug is set as Low priority, I know that maybe it seems not so important but for me as Product Owner of multiple products I want that my Scrums teams follow the order I have defined in the Backlog. There is some workaround?

Craig Marsden_fzhbwd

We've tried this recently and have encountered the same issue (backlog, top image; board, bottom image). Before raising a new ticket (as suggested) are other users still experiencing this? Is there something I'm missing when enabling "group by"? I thought maybe it's because of the issue types, but tested that out and it still orders them differently.

backlog order (1).jpg

board order (1).jpg

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