Group a Jira board by assignee, priority, or any field
On a Jira board, columns always mean status: To Do, In Progress, Done. If you want to group work a different way — by assignee, by priority, by epic — Jira's answer is swimlanes: horizontal lanes layered on top of the status columns. They work, but they're configured in board settings, often need JQL, and only an admin can change them. Here's how to set up grouping in both space types, and how BetterBoard lets you group by any field from a menu.
Company-managed board
Company-managed boards offer the richest swimlane options. You can group by a preset like Assignee, Epic, or Space, or define fully custom lanes with JQL. Configuring them requires admin or board-admin access, and the setting applies to everyone using the board.
-
Open Board settings → SwimlanesFrom your board, select more (•••) → Configure board (or Board settings → Layout → Swimlanes). You must be a Jira admin, space admin, or board admin.
-
Choose a swimlane basePick a built-in option: Assignees, Stories (parent), Epics, Spaces (handy on multi-space boards), Queries for custom lanes, or No Swimlanes.
-
If you chose Queries, write a JQL clause per laneEach lane is its own query, e.g.
priority = Highestfor a "Critical" lane,priority = Highfor the next. Order them top to bottom. -
SaveThe swimlanes apply to the board for everyone. Work items that don't match any lane fall into a default catch-all lane.
Team-managed board
Team-managed boards support swimlanes too, but with a shorter list of preset options and the same admin requirement. Expect fewer choices than company-managed.
-
Open Board settings → SwimlanesFrom your board, select more (•••) → Board settings, then Swimlanes. Board-admin or space-admin access is required.
-
Choose from the available presetsTeam-managed swimlanes are more limited: typically grouping by assignee, epic/parent, or subtask. Custom JQL lanes are a company-managed strength, not a team-managed one.
-
SaveAs with company-managed, the swimlane choice applies to the whole board, not just your view.
BetterBoard for Jira
BetterBoard doesn''t hard-wire columns to status. You choose what the board groups by, and you can change it whenever you like, without admin rights or JQL.
-
Pick the field to group byOpen the board''s grouping setting and choose a field: status, assignee, priority, sprint, labels, or any single-select custom field. The board re-lays-out instantly: group by assignee for a standup, by priority for triage, by epic for planning, then switch back. No board-settings dive, no JQL, no admin permission.
Good to know
What to know about grouping Jira boards:
- Columns always mean status. Native Jira boards can''t make columns represent assignee, priority, or any other field: swimlanes are the only grouping lever.
- Admin-only. Only Jira, space, or board admins can change swimlanes. Regular board users can''t re-group on their own.
- It''s shared, not personal. Swimlane settings apply to everyone on the board; whatever an admin sets is what the whole team sees.
- Custom grouping means JQL. Anything beyond the presets requires a JQL query per lane, and only in company-managed spaces.
- Team-managed has fewer options. The preset list is shorter, columns remain locked to status, and there''s no rich custom-query swimlane support.
- Catch-all lane. Work items that match no defined lane collect in a default lane, which can get noisy.
Group by anything, in one click
Assignee, priority, epic, sprint, label, or any single-select custom field: BetterBoard groups your board however you need, without JQL or admin rights. Free to try with your Jira.