bcd3dd563ec3
Not that I am aware of. Read the comments below and have a big laugh. Or cry. I would understand either way...

Hi, Is there an update on this issue? Is there a workaround for this issue without having to create ghost sub-tasks? 

Thanks

I just starting managing a project using JIRA, saw this problem (basing swimlanes on stories doesn't show stories in priority order) in the fall of 2023, disheartened to see it was first reported 9 years ago and has never been fixed.

Am thinking we should use a different tool with better agile support - this is basic stuff that should have been fixed years ago.

Still a real-world problem this one. Reading through the comments I have little hope this will ever get fixed. It's sad to see how long this has been dragging on

Should we organize something for its 10th anniversary?

Request Created

Moved to "Gathering Interest" four years later

Still in "Gathering Interest"  four and a half years later

Ya know, I think they might not bother to do anything with this one. Call it a hunch.

The solution for https://jira.atlassian.com/browse/JSWCLOUD-21508 would also cover this issue. Why does Jira forget about prioritization and ignore the built-in "story by swim-lane" functionality just because no sub-task exists?

If this was intentional, I'd like to better understand the reasoning behind it because it seems like this issue is really a bug.

Please fix this, dear Jira overlords.

I've upvoted this problem a while ago. Since then, we used to do exactly what @Corinna suggested.

Since then, we have moved from Scrum to Kanban and our work items are so small, that if we even could define subtasks, we split it up. We no longer use or require subtasks.

@Corinna has the only answer I've ever figured out.  It's a pain, but if I actually want to have the priority represented I add a subtask of "needs subtasking".  

Hi Caitlin,

I agree this is a really annoying thing which we've been waiting a long time for Atlassian to fix. Perhaps with all these recent comments they may consider taking another look.

The workaround we use (though by no means ideal) is to create subtasks under the ticket even if you wouldn't do normally. This will force the story/bug level ticket to become a swimlane in the correct priority place on the board (according to the order on the backlog view). It's annoying though because sometimes for things like bugs and spikes you don't necessarily need/want sub-tasks. We just create a sub-task with the same name as the story and move the sub-task across the board instead of the story/bug itself.

Hope this may have been of some help.

Regards,

Corinna