Ordering Issues in Board using by stories swimlane and non subtasked issues sitting at bottom board

[louise.campbell]

Our team is used to having our board set up with stories and their subtasks as the swimlanes. It gives us a nice view as the subtasks relating to that story move across the board columns.

The other items that are in the form of a task and don't therefore have subtasks then sit at the bottom of the board. It's manageable but I would much rather prefer that the board presented the work, irrespective of the Issue type, in the order that i have ordered it in my sprint backlog as I work hard with my team to ensure that we are pulling in work based on priority. When we use the board at stand it, it feels harder than it needs to be as the work doesn't present on the board in the desired order.

I have experimented with the Queries in swimlanes and tried with components and labels but I haven't really gotten anywhere. I'd rather just be able to keep the Story / subtask layout and be able to drag and drop the order of the 'task' type issues as they should be.

Does anyone have any suggestions please on how to handle this?

Thank you

Louise

[Earl McCutcheon]

Hello @louise.campbell

Thanks for reaching out, and when swimlanes are set to Story, the stories without any subtasks will be sent to the bottom without an option to change this behavior, as covered in:

• Configure swimlanes

Stories: One parent issue per swimlane (i.e. each swimlane contains all of the parent's sub-tasks), with issues that have no sub-tasks appearing below.

So arranging the boards by a swimlane metric other than the story would be the only option.

We have the following feature request in place for cloud and server respectively to add this in, make sure to add a vote to show your interest in the feature:

• https://jira.atlassian.com/browse/JSWSERVER-6053
• https://jira.atlassian.com/browse/JRACLOUD-66698

Regards,
Earl