Configure Swimlanes in Jira
Use swimlanes to group a board by a planning question such as ownership or epic. Grouping changes presentation, not the underlying issue status or permission model.
Step-by-step guide
Check access and scope
Check whether the board is company-managed or team-managed before following configuration steps. Company-managed swimlane configuration requires board administration access.
Choose a grouping question
Choose the grouping question before changing the board.
Open swimlane controls
Open company-managed Board settings and Swimlanes or the supported Group by control.
- Worked example: For a release review, group by epic when discussing outcomes; group by assignee when discussing handoffs. If using priority queries, ensure urgent work is not hidden by an overly narrow lane.
Select the grouping
Choose a built-in grouping or carefully scoped query lanes.
Inspect overlapping lanes
Review issues that match several query lanes and the fallback lane.
Clear unrelated filters
Inspect the board with active quick filters cleared.
Verify the result
Representative issues appear in understandable lanes and uncategorized work remains visible.
Common mistakes
Avoid the main failure mode
A lane is not a new team or an access boundary. Sensitive records still require actual issue permissions.
Check the handoff edge case
Leaving a quick filter active while assessing lanes can hide expected work. Clear unrelated filters during validation.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.