Would anyone else find priority-based grouping with drag & drop useful on Kanban boards or just me?

[Sarah Rosenthal]

Hi everyone,

I’m curious whether other teams have run into the same limitation on Jira Kanban boards.

Ideally, I would like issues to be automatically grouped and ordered by priority, while still being able to manually rearrange issues within the same priority group.

For example, a column such as Ready might contain 20 issues across several priority levels. I would like the board to:

1. Keep all issues grouped by priority, with Highest at the top and Lowest at the bottom.
2. Allow drag & drop between issues with the same priority.
3. Prevent issues from being dragged across priority boundaries.

This would mean that I could freely rearrange 12 Medium-priority issues, but a Medium issue could not be placed above a High-priority issue or below a Low-priority issue.

At the moment, the available options do not seem to fully support this:

• Using ORDER BY priority DESC in the board filter keeps issues sorted by priority, but disables manual ranking.
• Using ranking allows drag & drop, but issues with different priorities can become mixed.
• Swimlanes by priority add visual complexity and do not provide the same constrained ranking behavior.
• Automation rules for adjusting rank can be complex and may not update the board in real time.

The behavior I have in mind would be similar to priority swimlanes, but without requiring separate swimlane configuration. Priority would act as a fixed grouping constraint, while rank would determine the order within each group.

Would this be useful for your team as well? How do you currently manage issue order when a Kanban column contains many issues with different priorities?

[Alexandre Pezzini]

Hi! You’ve hit on one of the most discussed limitations of Jira Kanban boards.

To be direct: Jira does not currently support a "hybrid" sort where you group by a field (like Priority) and then manually rank within that group. Drag-and-drop ranking is strictly tied to the Rank field, and adding any other ORDER BY clause to your board filter will disable it.

There is a long-standing feature request for this (https://jira.atlassian.com/browse/JSWCLOUD-692), but as it has been open since 2008, it is unlikely to be implemented soon.

How most teams handle this today:

1. Priority Swimlanes (Visual Grouping): This is the closest you can get to your requirement. Set your board swimlanes to be based on Priority. This creates horizontal "groups" for High, Medium, and Low. You can still drag and drop issues to rank them within each swimlane.

2. Automation "Auto-Rank" (The "Constraint" approach): You can create an Automation flow that triggers when an issue is created or its priority changes. The action would be to "Move to top of backlog" for High priority or "Move to bottom" for Low. This keeps your Rank field roughly aligned with your Priority without breaking the drag-and-drop functionality.

3. Quick Filters: Keep the board ordered by Rank ASC but create Quick Filters for each Priority level. This allows you to "zoom in" on all Medium issues, rank them, and then turn the filter off to see the full list.

Summary: If you need that fixed grouping, Swimlanes are your best bet. If you need a single vertical list, you'll need to stick with ORDER BY Rank ASC and use Automation or Quick Filters to help manage the manual effort.

Sources:

• https://jira.atlassian.com/browse/JSWCLOUD-692

• Implementation of New Features Policy | Atlassian Support | Atlassian Documentation

• Unable to drag and drop to reorder issues on a Kanban Board in Jira | Jira and Jira Service Management | Atlassian Support