How to Create a Kanban Board in Jira: 7 Simple Steps in 2026
Need a clearer workflow? Learn how to create a Kanban board in Jira in 7 simple steps and spot blockers. Read now to get started.
A Jira project can feel chaotic when requests, bugs, and in-progress work sit in different places. Without a shared view, you may miss blockers, overload teammates, or keep starting tasks while older work stalls. That makes it harder to answer a simple question: what should move next?
A Kanban board gives your team a visual workflow, from incoming work through completion. Jira can create one for a project or a saved filter, then let you tailor columns, cards, and limits to match how your team works. Here’s how to set one up in seven practical steps. I’ll also explain how to keep it useful after launch, so your board becomes a working tool rather than another screen people forget to check.
Create a Kanban Board in Jira: 7 Steps
To create a Kanban board in Jira, open the board creation option, choose a project or saved filter, and configure the columns to match your workflow. Then set clear work-in-progress expectations and review the board with your team. Jira’s interface can vary slightly by plan and navigation layout, but these steps cover the core setup.

1. Map the workflow you want to see
Before opening Jira, list the stages work passes through today. A small product team might use Backlog, Selected, In Progress, Review, and Done.
Keep the first version simple. If your team cannot explain when a task moves between two columns, those stages may be too detailed or unclear.
2. Choose the project or work you want to track
Decide whether the board should show work from one Jira project or a broader selection. A single-project board suits a team managing one product area. A cross-project board can help when related work lives in several projects.
For a board spanning multiple projects, you may need a saved filter that captures the right issues. Check that the people who need the board can access the projects and filter results.
3. Open Jira’s board creation option
In Jira, open the Boards menu and choose the option to view all boards. Select Create board, then choose a Kanban board when Jira asks what type you want.
If your navigation looks different, use Jira’s board search or project navigation to find the board creation control. The labels and menu locations can change between Jira experiences.
4. Name the board and choose its location
Give the board a name that tells people what work it covers, such as Mobile App Support or Website Improvements. Choose a location that makes sense for the team or project.
A specific name helps prevent confusion when a Jira site has several boards. For example, Team Kanban gives less context than Payments Bug Fixes.
5. Select a project or saved filter
Choose the project you selected earlier, or connect the board to a saved filter. Review the filter criteria before creating the board; a filter that excludes a work type can make important tasks disappear.
For example, a support board might include bugs and service requests while leaving out unrelated project work. Ask a teammate to verify that expected issues appear before you move on.
6. Match columns to your team’s workflow
Open the board settings and adjust its columns. Map each status to the stage where the team expects to see that work. If a status has no clear column, cards can be hard to find or appear in an unexpected place.
Keep column names familiar to the people doing the work. If your team calls review “QA,” a column labeled Quality Check may slow down everyday use.
7. Set working agreements and test the board
Decide what qualifies as active work, who can move an issue, and how the team handles blocked tasks. Jira lets you configure board settings such as card details and, depending on your setup, work-in-progress limits.
Move a few real issues across the board and confirm that the columns, filters, and permissions behave as expected. Then invite the team to use it during a short planning or daily check-in.
What a Jira Kanban Board Shows
A Kanban board displays work as cards arranged in columns. Each card represents an issue, such as a bug, task, or service request, while its column shows the issue’s current workflow stage.
That visual view makes bottlenecks easier to spot. If cards collect in Review while In Progress stays relatively clear, your team may need more review capacity or a faster handoff.
Jira boards can also show useful issue details on cards, depending on configuration. A team might display priority, assignee, or due date, giving people context without opening every issue.
Configure Columns Around Real Work
Columns should represent meaningful stages, rather than every small action. A marketing team could use Ideas, Ready, In Progress, Review, and Published. That gives the team enough detail to coordinate without making the board cumbersome.
Here's why: the board is only useful when its workflow reflects what actually happens. If a task goes through several informal review steps, group them unless the team needs to manage each step separately.
Clarify what “done” means
Write down what must be true before an issue moves into each column. For example, a card might enter Review only when the work is complete and ready for another person to check.
These agreements reduce inconsistent updates. One teammate’s idea of “done” may mean coding finished, while another expects testing and approval.
Keep status mapping understandable
Jira issues have statuses, and boards place those statuses into columns. Review the mapping so each status lands where the team expects it. If several statuses share a column, make sure the distinction still matters to your workflow.
Try the setup with a few live issues. If people repeatedly ask where a card belongs, simplify the mapping or explain the transition rule.
Use Work-in-Progress Limits Without Slowing the Team
A work-in-progress limit sets a target or cap for how many issues should occupy a particular stage. For example, a team might aim to keep no more than four cards in Review at once.
The purpose is to reveal overload, not to create a contest. When a column reaches its limit, the team can help finish existing work before starting more tasks. Jira’s exact options may depend on the board and configuration.
Choose a limit the team can test
Start with a reasonable number based on team size and the work involved. If a three-person team routinely has eight tasks underway, try a lower target and see whether handoffs improve.
Review the result after a week or two. Adjust the limit when it creates useful conversation or when real work patterns show that the number is unrealistic.
Build a Simple Routine Around the Board
A board needs regular attention to stay accurate. During a short check-in, review blocked cards, work approaching completion, and any column where issues are accumulating.
For example, a team might notice that three tasks are waiting on the same approval. That observation can lead to a specific action, such as asking the approver to review them together.
Keep cards current and actionable
Update the assignee, status, and priority when the situation changes. Add a short note when an issue is blocked, including what needs to happen next and who can help.
Small updates make the board more trustworthy. If the board says a task is active but the work has been waiting for days, teammates may stop relying on it.
Review flow, not just completed work
Look for repeated delays, long queues, and work that gets reopened. Jira’s built-in reporting can help teams inspect patterns, while regular conversation explains what caused them.
A rising queue in Testing, for instance, may point to limited testing capacity or unclear acceptance criteria. Use that signal to improve the workflow rather than blame an individual.
Kanban Project Management with ONES.com
ONES.com brings project management and knowledge management together in a unified platform. ONES Project is its project management product and a Jira alternative; ONES Wiki provides knowledge management as a Confluence alternative. They are sold separately.

The platform may suit teams that want configurable workflows, project visibility, and knowledge tools across cloud or self-hosted deployments. Its free plan supports up to 30 seats, and deployment options include Cloud, On-Premise, Private Cloud, and Air-gapped environments.
Core capabilities: team pain to practical result
- Work is split across disconnected tracking practices: ONES Project provides project and task management in one workspace, helping teams maintain a shared view of active work.
- Jira workflow changes feel restrictive: Jira-compatible workflows, custom workflows, and custom fields let teams adapt issue tracking to their process.
- Teams need to manage iterative delivery: Sprint management supports planning and tracking work across development cycles.
- Progress is hard to assess: Built-in reporting gives teams a way to review project status and identify work that needs attention.
- Routine actions take repeated manual effort: Automation can handle selected workflow actions and reduce repetitive coordination.
- Plugin dependence adds operational overhead: Native capabilities can reduce the need for extra plugins for common project management needs.
- Teams require controlled hosting: Cloud, On-Premise, Private Cloud, and Air-gapped deployments offer different hosting choices.
- Self-hosted teams worry about missing features: ONES.com offers full feature parity between its cloud and self-hosted versions.
Application scenarios
A software team moving from Jira could use ONES Project to configure issue workflows, manage sprints, and review project progress. Teams can evaluate whether its Jira-compatible workflows match the stages they already use.
A security-conscious organization may need work tracking in a restricted environment. Its On-Premise, Private Cloud, or Air-gapped deployment options can support that requirement, while ONES Wiki can be considered separately for knowledge management.
The best fit depends on your workflow, hosting needs, and preferred project setup. Map those requirements before comparing platforms, then test the essential work stages with a small team.
Common Kanban Board Challenges
Cards do not appear where teammates expect
Problem: An issue may be missing because the board filter excludes it, its status is not mapped, or someone lacks access. Solution: Check the board filter, status-to-column mapping, and project permissions before changing the issue itself.
The board has too many columns
Problem: A separate column for every small handoff creates clutter and makes movement harder to understand. Solution: Combine stages that do not need separate tracking, then split them only when the team needs to act on the distinction.
Work piles up in one stage
Problem: A growing queue can signal an overloaded stage, unclear requirements, or a slow approval. Solution: Identify the recurring reason with the team, then adjust capacity, handoffs, or entry criteria.
People stop updating the board
Problem: A board loses credibility when cards do not reflect current work. Solution: Keep the board review short and useful, assign clear ownership for updates, and remove fields or steps that do not help decisions.
Frequently Asked Questions
Can I create a Jira Kanban board from an existing project?
Yes. During board creation, you can choose a project as the board’s basis. Jira then displays matching issues according to the board setup. Before relying on it, check the project selection, status mapping, and team permissions so expected work appears in the right place.
Can one Jira board show issues from multiple projects?
It can, when the board uses a saved filter that includes issues from the relevant projects. Make sure the filter criteria capture the work you intend to track and that board viewers have permission to see those projects. Test with representative issues before sharing the board widely.
What is the difference between a Kanban board and a Scrum board in Jira?
A Kanban board focuses on continuous flow through workflow stages. A Scrum board is organized around sprint planning and sprint execution. A team handling incoming support work may prefer Kanban, while a team delivering planned batches of work may use Scrum. Jira provides different board types to support these approaches.
Can I change a board’s columns after creating it?
Yes. Board settings let you adjust columns and map Jira statuses to them. Make changes carefully if the team already uses the board, because a changed mapping can alter where existing issues appear. Test the revised setup with a few issues and explain the change to the people who rely on it.
Does a Kanban board automatically limit how much work a team starts?
No. A board shows work, but the team needs shared agreements about what to start and how to respond when a stage is overloaded. You can use work-in-progress limits where available, then discuss them during regular board reviews. The limits work best when they guide decisions rather than serve as rigid quotas.
Conclusion
Creating a Jira Kanban board starts with a clear workflow, a relevant project or filter, and columns that match how work moves. The seven setup steps help you create the board, test its issue visibility, and agree on practical working rules.
But here's the truth: a board cannot fix unclear handoffs on its own. Review it regularly, keep cards current, and use queues as clues about where work gets stuck. If your team’s needs extend beyond Jira, compare platforms against your workflow and hosting requirements before making a change.