Group a Jira board with swimlanes
Jira software board columns represent status. Swimlanes add another grouping, such as assignee or epic. Company-managed boards offer shared swimlane configuration; the newer team-managed board lets people personalize grouping from the toolbar. Choose the path that matches your board. Use the illustrated example to see how rows and columns work together, then choose a grouping for the task.
Group by any field
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 → Swimlanes
From 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 base
Pick 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 lane
Each lane is its own query, e.g.priority = Highestfor a "Critical" lane,priority = Highfor the next. Order them top to bottom. -
Save
The swimlanes apply to the board for everyone. Work items that don't match any lane fall into a default catch-all lane.
Group without JQL lanes
Group by the field that matters without configuring shared swimlanes.
Use the Group menu on the newer team-managed software board for personal grouping. Admins can save a team default separately.
-
Open the Group menu
On the board toolbar, open Group and choose an available field, such as assignee, priority, or epic. -
Review the lanes
Expand the lanes you need. For example, group by assignee for a standup and by epic for a planning review. -
Keep personal and team defaults separate
Your personal grouping can differ from the team default. An admin can save a default board view for the team; that is a separate action from changing your own view.
Go beyond Jira’s preset lanes
Group by the field that matters, not just Jira’s limited choices.
What are swimlanes in Jira?
Swimlanes are horizontal rows that group work items across the status columns of a Jira board. A card still sits in its workflow column, such as In progress, but also belongs to a row, such as its assignee. Grouping changes how you see the work; it does not change the card’s status or assignee.
In this illustrative board, Alex owns one item in To do and one in In progress. Sam owns an item in Done. Reading across a row shows one person’s work by status; reading down a column shows work at the same workflow stage across people.
| Assignee swimlane | To do | In progress | Done |
|---|---|---|---|
| Alex | Draft release notes | Review onboarding copy | No items |
| Sam | No items | No items | Publish help guide |
Choose a swimlane grouping for the task
Start with the question you need the board to answer. Assignee works for a standup; epic works for a planning review. On company-managed boards, choose a preset or define Queries. On the newer team-managed software board, choose from the fields in its Group menu; that menu is not a custom JQL swimlane editor.
| Grouping | Useful when | Setup and limits |
|---|---|---|
| Assignee | Discuss who is working on what at a standup. | Use the Assignees preset or the team-managed Group menu. Check the unassigned work too. |
| Epic | Review progress across larger pieces of work. | Use Epics or the available epic grouping. Work without an epic needs attention as well. |
| Space or project | Keep work from several spaces recognisable on one board. | Use the company-managed Spaces preset on a board that already includes those spaces. Grouping does not add spaces to the board. |
| Priority | Keep urgent work visible during triage. | Use Queries on a company-managed board or the priority option on the newer team-managed board. |
| Custom query | Group by a condition that no preset covers. | Company-managed Queries uses one JQL clause per lane. Unmatched items remain in Everything Else. |
| No swimlanes | Keep a small board easy to scan without extra rows. | Choose No Swimlanes on a company-managed board. |
Example swimlanes for priority triage
On a company-managed board, select Queries as the swimlane method. Add a lane named Critical with priority = Highest, then a High lane with priority = High. These are example priority names; use the values configured on your Jira site.
Put Critical above High in the lane order. A Highest-priority item in In progress should appear at the intersection of the Critical row and In progress column. A High-priority item stays in its current status column in the High row. Lower-priority work remains in Everything Else; it has not disappeared from the board.
Check a known item in each category before using the view for triage. On the newer team-managed software board, use Group → Priority instead; the custom lane names and query editor above describe the company-managed route.
When to use a filter instead of swimlanes
Swimlanes organise the work currently on the board into rows. A filter narrows that work to a subset. Group by assignee when you want to discuss everyone’s work together; apply an assignee filter when you only want to see one person’s work.
If custom lanes produce many nearly empty rows, keep a broader grouping and use a filter for the temporary question. For example, keep epic swimlanes for planning and filter to one assignee for a handover. The filter does not reconfigure the shared swimlane method. See filtering a Jira board for the controls available in each board type.
Troubleshoot missing or unexpected swimlanes
No swimlane settings? Check the board type first. Company-managed configuration requires the appropriate board or space admin access. On the newer team-managed board, look for the Group menu for your personal view rather than the company-managed Queries editor.
An item is in Everything Else? Compare its actual field values with the lane query. The default row holds work that matches none of the query lanes. Test the clause in Jira search and confirm it matches the item you expected.
A row looks empty or work is missing? Expand collapsed lanes and clear temporary filters before changing the configuration. Swimlanes only group work already included on the board. Check the underlying board filter and status-column mapping if the item is still missing; see the missing-work guide.
Too many rows? Use a broader preset or fewer query lanes, then filter for narrower questions. On team-managed boards, check whether you are looking at your own personalised grouping or the saved team default before asking an admin to change it.
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.
- Custom grouping means JQL. Anything beyond the presets requires a JQL query per lane, and only in company-managed spaces.
- Catch-all lane. Work items that match no defined lane collect in a default lane, which can get noisy.
- Shared company-managed swimlanes and personal team-managed grouping are different controls. Check the board type before looking for admin settings.
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.