How to Create a Kanban Board in Jira: Step-by-Step Guide
Need a clearer workflow? Learn how to create a kanban board in jira, set columns, WIP limits, and filters. Click to discover the steps.
A Jira board can make work easier to follow, but the setup can feel confusing when projects, filters, statuses, and board settings all overlap. If you pick the wrong project or map statuses poorly, cards may disappear or pile up in the wrong column.
That frustration can turn a simple visual workflow into another thing your team has to maintain. The good news is that you can create a Kanban board in Jira in a few steps, then adjust it to match how work actually moves.
I’ll walk you through board creation, column setup, work-in-progress limits, and useful filters. You’ll also see how to avoid common setup problems so your board stays clear as work changes.
How to Create a Kanban Board in Jira
A Kanban board in Jira is a visual view of work items arranged in columns that represent stages of progress. To create one, choose a project or saved filter, create a Kanban board, and configure its columns to match your team’s workflow.
- Choose the project and workflow. Decide which team or work you want the board to show. Confirm that you can access the project and that its statuses reflect the stages your team uses.
- Open the board creation option. In Jira, go to Boards and choose View all boards, then select Create board. Navigation labels can vary by Jira version and permissions.
- Select a Kanban board. Choose the option to create a Kanban board. Jira may offer choices to create one from a project or from an existing saved filter.
- Choose what the board displays. Select a project when the board should focus on one project. Choose a saved filter when you need work from multiple projects or a more specific set of issues.
- Name the board and choose its location. Use a clear name, such as “Customer Support Kanban” or “Website Release Work.” Select an appropriate location, then create the board.
- Check the columns and statuses. Open the board settings and review the column setup. Map each relevant Jira status to the correct column so cards move through the board as expected.
- Test the board with real work. Open a few issues, move them through the workflow, and check that they appear in the right columns. Adjust settings before inviting the wider team to rely on the board.
But here's the truth: creating the board is only the beginning. The board becomes useful when its columns and rules match the way your team handles work.

Choose a Project or a Saved Filter
The choice determines which work appears on the board. A project-based board is usually the simplest option when one team works in one Jira project.
For example, a support team might create a board from its service project and track incoming requests through “Open,” “Investigating,” and “Resolved.” Jira applies the project scope, so the team can start without building a complex filter.
A saved filter makes sense when the board needs to show issues across projects or only certain work types. A release manager, for instance, may need a view of issues tagged for an upcoming release across several development projects.
Check access before choosing a filter
Board visibility depends on the permissions attached to its filter and the projects it includes. If teammates cannot see some cards, check that they can view the relevant projects and access the saved filter.
Keep the filter focused. A board that combines unrelated work may look comprehensive, but it can make ownership and priorities harder to understand.
Set Up Columns That Reflect Real Work
Columns should represent meaningful stages, not every small action. A simple board might use “To Do,” “In Progress,” and “Done.” A team with review needs could add “Ready for Review” between active work and completion.
Here's why: Jira issues move according to workflow statuses, while columns are the visual groups shown on the board. If a status is not mapped to a column, an issue using that status may not appear where the team expects.
Map statuses deliberately
Open the board settings and review the column configuration. Move each status into the column that describes its current state, and check for statuses that are unmapped or placed inconsistently.
For example, a “Code Review” status should usually appear in a review column, not “In Progress” if your team treats review as a separate queue. A clear mapping helps people understand what needs attention.
Use a Kanban backlog when work needs a staging area
Some teams want a backlog for ideas or approved work that is not ready to enter the active flow. Jira can support a Kanban backlog, depending on the project and board configuration.
Keep the backlog distinct from active work. If every unstarted idea appears beside current commitments, the board may look crowded before the team has even begun its work.

Use Work-in-Progress Limits and Helpful Board Features
Work-in-progress limits help teams notice when too many issues are being handled at once. You can set a limit for a column, such as no more than four cards in “In Progress.” The limit is a prompt to discuss bottlenecks, not a substitute for team judgment.
The best part? A small limit can make hidden queues visible. If “Ready for Review” stays above its limit, the team can investigate whether reviews need clearer ownership or more capacity.
Make the board easier to scan
- Swimlanes: Group work by assignee, priority, epic, or another useful category. Use them only when the grouping answers a real planning question.
- Quick filters: Add shortcuts for common views, such as “My issues,” “Bugs,” or a particular release. These help teammates narrow the board without changing its overall scope.
- Card colors: Use color rules to highlight a meaningful detail, such as priority or issue type. Too many colors can make the board harder to read.
- Issue details: Choose the card fields that help people make decisions at a glance. A team may prefer to see assignee and priority rather than several rarely used fields.
Start with one or two features, then ask whether they help the team spot work that needs action. If a setting adds visual noise, remove it.
Keep the Board Useful as Work Changes
A Kanban board needs occasional maintenance. New statuses, changed project scopes, or outdated filters can make its view inaccurate over time.
For example, imagine a team adds a “Waiting for Approval” status but never maps it to a board column. Issues may seem to vanish when they enter that status, even though they remain in Jira.
Review board health during team check-ins
Ask whether columns still match the team’s process, whether old issues are stuck, and whether the board shows the right work. A brief review during a regular planning meeting can catch problems early.
You might be wondering: how often should you review it? Check after workflow changes and whenever teammates report missing or confusing cards. Otherwise, a monthly review is often enough for a stable process.
A Jira-Compatible Kanban Option: ONES.com
ONES.com brings project management and knowledge management together in one platform, with ONES Project for project management and ONES Wiki for knowledge management. They are sold separately, so teams can choose the product that fits their needs.

If your team wants a Jira alternative with Kanban-style project tracking, ONES Project offers Jira-compatible workflows, reporting, sprint management, automation, and customizable workflows and fields. Those capabilities can help teams organize work without relying on a large collection of plugins.
Where ONES Project may help
- Work is scattered across views: ONES Project gives teams a project management space with work tracking and reporting, helping people see progress without switching between several separate tools.
- Existing processes are hard to reproduce: Jira-compatible workflows and customizable fields let teams represent established stages and issue details. The result can be a familiar transition for teams already accustomed to Jira workflows.
- Teams need more visibility: Built-in reporting helps teams review progress and spot work that may need attention, without depending on extra reporting plugins for every view.
- Several work types need different rules: Custom workflows and automation let teams tailor processes and reduce repetitive handoffs, so a support queue and a development project do not have to follow identical steps.
- Teams plan work in cycles: Sprint management supports teams that combine iterative planning with visual tracking. Kanban-oriented teams can organize their flow around the stages they use.
- Plugin maintenance is becoming a burden: Native project management capabilities can reduce the need for plugins to cover common tracking and reporting needs. Teams can evaluate which add-ons remain essential instead of assuming every function requires one.
- Deployment requirements vary: ONES.com is available as Cloud, On-Premise, Private Cloud, and Air-gapped deployments. This gives organizations options for different infrastructure and network constraints.
- Cloud and self-hosted teams need consistency: The product offers full feature parity between cloud and self-hosted versions. Teams can evaluate deployment choices without treating one version as a reduced feature set.
Practical scenarios
A software team moving from Jira could recreate its issue stages and custom fields in ONES Project, then assess how its daily Kanban flow and reports work. A team with strict network controls could also evaluate an On-Premise, Private Cloud, or Air-gapped deployment.
For a smaller team, the free plan supports up to 30 seats. ONES.com can be worth evaluating when deployment flexibility or reduced plugin dependence matters, while Jira remains a sensible choice for teams already satisfied with their setup.
Common Challenges When Setting Up a Jira Board
- Cards do not appear: Check the board filter, project permissions, and status mapping. An issue may be outside the filter or using a status that is not assigned to a board column.
- The board feels overcrowded: Narrow the filter, archive completed work where appropriate, or use quick filters for common views. Avoid adding every project issue if the team needs to focus on a smaller flow.
- Work gets stuck in one column: Review the column’s work-in-progress limit and ask what is blocking movement. For instance, a review queue may need clear ownership rather than another status.
- Teammates interpret columns differently: Agree on what each stage means and when an issue moves forward. A short description of “Ready for Review” can prevent one person’s finished work from becoming another person’s ambiguous queue.
- The board changes without warning: Limit who can edit board settings and communicate meaningful filter or workflow changes. A quick check after a project update can prevent confusion during the next team meeting.
Frequently Asked Questions
Can I create a Kanban board without creating a new Jira project?
Yes. You can create a board from an existing project or an existing saved filter, depending on your Jira access and configuration. This lets you create a new visual view without creating another project. Before choosing a filter, check that the teammates who need the board can access both the filter and the included projects.
What is the difference between a Jira project and a Kanban board?
A project is where Jira issues and project configuration are organized. A board is a view that displays issues from a project or filter as cards in columns. One project can support multiple boards, and a board can include issues from more than one project when its filter is configured for that scope.
Why are some Jira issues missing from my board?
Start by checking whether the issue matches the board’s filter and whether you have permission to view its project. Then inspect the issue’s status and the board’s column mapping. If a status is not mapped, the issue may not appear in the expected column. Also check any quick filters that might be active.
How many columns should a Kanban board have?
Use enough columns to show meaningful stages, but avoid splitting the workflow into tiny steps. Three columns may work for a small team with a simple flow. A team that tracks review or approval separately might need additional columns. If people cannot explain why a column exists, consider combining it with a nearby stage.
Can I set work-in-progress limits in Jira?
Jira Kanban boards can support column limits, depending on the board and configuration. A limit indicates how much active work the team aims to hold in a stage. If a column exceeds its limit, use that as a signal to discuss workload or blockers. The limit should support a useful conversation rather than encourage people to hide work.
Conclusion
To create a Kanban board in Jira, choose the right project or saved filter, create the board, and map statuses to columns that match your real workflow. Then add only the settings that help your team make decisions.
If cards go missing or queues become crowded, check filters, permissions, column mappings, and work-in-progress limits. A few deliberate adjustments can turn a basic board into a practical view of work, while a brief review keeps it useful as your process changes.