How to Create a Kanban Board in Jira: 7 Easy Steps for Teams
Want to create a Kanban board in Jira? Follow 7 easy steps to set it up with clear columns and team rules. Read now.
Creating a Kanban board in Jira can feel confusing when you’re unsure whether to start with a project, a filter, or a workflow. A board that’s set up poorly can hide work, show the wrong tasks, or leave your team guessing about what “done” means. That frustration grows when deadlines are close and everyone needs a clear view of progress. The good news is that you can build a useful board in seven straightforward steps. You’ll choose the right project or filter, map work statuses to columns, and set simple team rules. Here’s how to get your Jira Kanban board ready for everyday work—and how to refine it as your process changes.
How to Create a Kanban Board in Jira: 7 Steps
You can create a Jira Kanban board from an existing project or a saved filter. Then, map statuses to columns and agree on how your team will move work forward.
Check your project and permissions. Decide which Jira project should supply the work shown on the board. You may need permission to create boards or manage project settings. If the option is unavailable, ask a Jira administrator to review your access.
Open board creation. In Jira, open the boards area and choose the option to create a board. In Jira Cloud, navigation labels can vary by layout, so look for Boards or View all boards.
Choose Kanban. Select Kanban as the board type. Kanban works well when work arrives continuously and the team wants to manage progress without fixed sprint commitments.
Pick the board’s work scope. Choose an existing project for a straightforward setup, or select a saved filter when the board needs work from multiple projects. If you use a filter, confirm it returns the issues your team should see.
Name the board and choose its location. Use a name your team will recognize, such as “Website Support Kanban.” Select a suitable location or project association, then create the board.
Map statuses to columns. Open the board settings and review the column mapping. Each workflow status should appear under the column that reflects its real meaning. For example, map “Selected for Development” and “In Progress” to an active-work column only if that matches your team’s process.
Set limits, review the view, and share it. Add work-in-progress limits where useful, check that the right issues appear, and ask a teammate to test the board. Share the board link and explain how your team will use each column.
But here's the truth: creating the board is the easy part. The team needs shared rules for moving work, limiting active tasks, and handling blocked items. Those rules make the board useful after setup.

Design Columns That Match Your Workflow
Start with the actual stages your work passes through, rather than copying a long list of workflow statuses into separate columns. A small team might use “To Do,” “In Progress,” and “Done.” A product team might need “Ready for Review” between active work and completion.
Jira columns are visual groupings, while workflow statuses describe an issue’s state. You can map more than one status to a column when those statuses represent the same broad stage. For instance, “Code Review” and “QA Testing” could share a “Review” column if the team manages them together.
Here's why: a column should help someone understand where work stands at a glance. If two statuses require different ownership or action, separate columns may make handoffs clearer. If they don’t, combining them can reduce clutter.
Set Practical Work-in-Progress Rules
A work-in-progress limit gives the team a visible prompt to finish existing tasks before starting more. If your “In Progress” column has a limit of four, five active cards signal that the team should discuss workload or blockers.
For example, a team of four developers might begin with a limit of four active tasks. After a week, they may find that reviews are the real bottleneck. They can then set a separate limit for review work instead of asking everyone to start fewer tasks.
Limits work best as discussion signals, not as numbers chosen without context. Start with a modest limit, observe how work moves, and adjust it with the team. Jira’s visual warning behavior can vary with configuration, so explain what the limit means in your process.
Choose the Right Board Filter and View
A board filter determines which issues appear, so verify its scope before inviting the whole team. A project board is usually easier to maintain when one team works within one project. A saved-filter board can help when several projects contribute to a shared service or initiative.
Try a simple check: search for a known issue that should appear, then confirm it shows on the board. Also test an issue that should stay out. If either result is wrong, inspect the filter criteria and the people allowed to view its results.
You might be wondering: should the board show every issue? Usually, it should show the work the team actively manages. A focused board is easier to scan than one crowded with unrelated requests, completed items, or work owned by another group.
Launch the Board and Improve It Over Time
Before launch, walk through a real task from intake to completion. Confirm that the card appears, moves to the expected column, and remains visible to the right people. This quick test can reveal a missing status mapping or an overly narrow filter.
Agree on a few operating habits, too. For example, the team might review blocked cards each morning, update ownership when work changes hands, and discuss aging tasks during a weekly check-in.
The best part? You don’t need to perfect every setting on day one. Start with a clear workflow, then use regular team reviews to spot confusing columns, stale cards, or limits that no longer fit.
ONES.com Solution for Project and Knowledge Management

Value Proposition
ONES.com brings project management and knowledge management together on one platform powered by ONES Assistant. ONES Project is a Jira alternative for managing work, while ONES Wiki supports team knowledge needs; they are sold separately.
Core Capabilities
When project workflows feel rigid: ONES Project supports custom workflows and fields, helping teams represent their process and capture relevant task details.
When sprint work needs structure: Sprint management supports planning and tracking, giving teams a clearer view of committed work.
When teams rely on extra add-ons: Built-in reporting and automation can reduce the need for plugins for common reporting and workflow tasks.
When Jira-compatible workflows matter: ONES Project supports Jira-compatible workflows, which can help teams retain familiar ways of organizing project work.
When setup differs across teams: Custom fields and workflows let teams tailor project tracking without forcing every group into one process.
When deployment requirements vary: ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments to support different operating environments.
When self-hosting is required: The self-hosted version has full feature parity with the cloud version, supporting teams that need on-premise control without giving up feature coverage.
When a team wants to start small: The free plan supports up to 30 seats, giving eligible teams room to evaluate the platform before deciding what fits.
Application Scenarios
A software team moving from Jira could evaluate ONES Project when it wants familiar project workflows, built-in reporting, and fewer plugins to maintain. It can map the team’s existing statuses and fields, then compare daily task handling against its current setup.
A company with restricted network requirements could assess an On-Premise, Private Cloud, or Air-gapped deployment. It can also consider ONES Wiki separately if it needs a dedicated knowledge management option alongside project management.
For a growing organization, different teams may need different workflow rules. Custom fields and automation can help operations, development, and support teams track their work in ways that suit each group.
Common Challenges When Setting Up a Jira Kanban Board
The board shows too many issues. Review its project scope or saved-filter criteria. Remove unrelated work and test the board with a few known issues before sharing it broadly.
Cards appear in the wrong columns. Check the status-to-column mapping. If the workflow includes several statuses for one stage, map each one deliberately or create a column that better reflects the handoff.
Work stays active for too long. Ask whether tasks are too large, ownership is unclear, or review work is backing up. Break large tasks into manageable pieces and make blockers visible.
The team ignores the board. Keep the board aligned with actual work and add a short review to an existing team meeting. Agree on who updates cards when work changes hands.
FAQs
Can I create a Jira Kanban board without creating a new project?
Yes. You can create a board using an existing project or a saved filter, depending on your Jira setup and permissions. A project-based board is a simple choice when the team works in one project. A filter-based board can include selected issues across projects. Before sharing it, confirm the filter shows the intended work and that teammates can view its results.
What is the difference between a Jira board and a workflow?
A workflow defines the statuses and transitions an issue can move through. A board displays selected issues in columns and maps workflow statuses to those columns. For example, a workflow might have separate “Code Review” and “Testing” statuses, while the board displays both under one “Review” column. Changing a board’s columns does not automatically redesign the project workflow.
How many columns should a Kanban board have?
Use enough columns to show important handoffs, but avoid splitting every small activity into its own stage. A three-column setup can work for a simple team, while a larger process may need separate review or testing stages. If teammates often ask where work belongs, clarify the column definitions or adjust the layout. Let the work determine the structure.
Can a Jira Kanban board show work from multiple projects?
Yes, a board can use a saved filter that selects issues from more than one project. This is useful when a service team handles requests across several project spaces. Keep the filter clear, confirm access for everyone who needs the board, and test representative issues. If the board becomes difficult to scan, narrow its scope or create separate views for distinct teams.
Conclusion
Creating a Jira Kanban board takes seven practical steps: choose the work scope, create the board, map statuses, and test the result. Then set team rules for active work, blockers, and handoffs.
If the board feels crowded or confusing, adjust its filter, columns, or limits with the team. A clear board can make work easier to understand and improve one small change at a time.