How to Create a Kanban Board in Jira: 7 Clear Steps in 2026
Need a clearer view of work in Jira? Learn how to create a Kanban board in Jira in 7 steps, map columns, and keep tasks moving. Read now!
A Jira Kanban board can make work easier to see and help your team move tasks through a clear workflow. Creating one is straightforward, but a poorly configured board can hide important work, show confusing columns, or let too many tasks pile up at once. That’s frustrating when your team needs a reliable picture of what’s in progress and what’s blocked.
Here’s the truth: creating the board is only the first part. You also need to connect it to the right project, map statuses to columns, and choose settings that fit how your team works. Follow these seven steps to build a useful Jira Kanban board, then refine it as your workflow changes.
How to create a Kanban board in Jira: 7 steps
Start by confirming that you have access to the Jira project and permission to create or manage boards. Menu names can vary slightly between Jira versions and configurations, but the setup follows the same basic path.
-

Choose the project and clarify the workflow
Decide which project the board should display and which work the team needs to track. A marketing team might need columns for “Ideas,” “Writing,” “Review,” and “Published,” while a software team may use “To Do,” “In Progress,” “Code Review,” and “Done.”
Check that the project’s statuses reflect those stages. If the workflow is unclear, ask the team to agree on what it means for a task to enter or leave each stage before you configure the board.
Open the board creation option
In Jira, open the board area, often under Boards or View all boards, and select Create board. In some Jira experiences, you can also start from a project’s board menu.
If you can’t see the option, check your permissions or ask a Jira administrator for help. Board creation and project access can depend on your organization’s settings.
Select a Kanban board
Choose the Kanban board type when Jira asks which board you want to create. Kanban displays work as cards moving across columns, so the team can see its current stage at a glance.
Choose a Scrum board only if your team plans work in time-boxed sprints and needs sprint planning features. For a continuous flow of tasks, Kanban is usually the better fit.
Decide whether to start with a project or a saved filter
Jira typically lets you create a board from a project or from an existing saved filter. A project-based board is a convenient option when you want to see work from one project.
A saved-filter board can include issues that match specific criteria, including work across multiple projects. For example, a support team could use a filter to show open service tasks assigned to its members.
Name the board and set its location
Give the board a clear name, such as “Mobile App Delivery” or “Customer Support Flow.” Choose a location that makes sense for the people who need to find and manage it.
Review the board details before you finish. A meaningful name helps distinguish this board from other team or project boards, especially when several groups use Jira.
Map workflow statuses to columns
Open the board settings and find the columns or column configuration. Map each relevant Jira status to the column that represents its current stage.
For example, map “Selected for Development” and “In Progress” to an “In Progress” column if both statuses mean work has started. Make sure the final column reflects completed work, and check that every active status appears somewhere on the board.
Review the board, then share it with the team
Open the board and check that the right tasks appear in the right columns. Confirm that cards show useful details, such as priority, assignee, or due date, if those details matter to your team.
Share the board with the people who need it and explain how the team will use it. Ask a few teammates to test the workflow, then adjust the settings if they spot missing tasks or confusing stages.
The best part? You can improve a board after creation. Start with the essential stages, observe how work moves, and revise the setup when the team finds a real problem.
Plan the workflow before you configure the board
A board works best when its columns represent meaningful stages of work. If “Review” includes several different activities, for example, you may need a clearer definition or a separate stage for testing.
Ask the team what must be true before a task moves forward. A developer might mark work ready for review only after code is complete and checks have passed. That shared understanding reduces handoff confusion.
Keep the first version simple. A small team could begin with “To Do,” “In Progress,” and “Done,” then add a review stage if work regularly waits there. Too many columns can make the board harder to scan.
Configure columns, cards, and work limits
Columns show where work stands, while cards carry details about individual tasks. Choose card fields that answer everyday questions quickly, such as who owns the task, how urgent it is, or when it is due.
Some Jira boards support work-in-progress limits for columns. A limit of four tasks in “Code Review,” for instance, can prompt the team to finish reviews before starting additional work. Treat the limit as a signal for discussion, not an automatic rule that solves delays by itself.
Swimlanes can also help separate work into useful groups, such as priority, assignee, or project. Use them when they make the board easier to read. If people need to scan several swimlanes before finding their tasks, simplify the arrangement.
Keep the board accurate and useful
A board only reflects the work people keep up to date. Encourage teammates to move a card when its status changes, add a note when a task is blocked, and close completed work promptly.
For example, if a task remains in “In Progress” after the work is complete, the team’s view of its capacity will be misleading. A short review during a stand-up or weekly planning session can catch outdated cards.
Check the board settings when the team’s process changes. A new testing step, different ownership pattern, or revised project filter may require updates so the board continues to show the right work.
Common setup mistakes to avoid
One frequent problem is creating a board before agreeing on the workflow. The result may be columns that no one understands or statuses that don’t match how work actually moves.
Another is using a filter that excludes important tasks. If the board is based on a saved filter, review its criteria and test whether expected work appears. A missing issue can be caused by the filter, permissions, or its project settings.
Teams can also overload the board with extra fields, swimlanes, and columns. Add a feature only when it helps answer a real question. A board should make it easier to spot work and delays, not require a tutorial to read.
Kanban workflow management with ONES.com
ONES.com is a unified platform for project management and knowledge management, powered by ONES Assistant. ONES Project handles project management and is a Jira alternative; ONES Wiki provides knowledge management as a Confluence alternative. ONES Project and ONES Wiki are sold separately.

If you’re evaluating how a team can manage work beyond a Jira board, compare the workflow, reporting, deployment, and administration needs you already have. The right fit depends on how your teams work and where they need to host their project management environment.
Core capabilities
- Issue tracking across stages: When work is difficult to follow, Jira-compatible workflows in ONES Project let teams organize tasks through familiar stages. That helps teams keep a consistent view of progress.
- Workflow customization: When a default process doesn’t match the way a team handles work, custom workflows and fields provide room to reflect the team’s actual steps. That can make task details and handoffs clearer.
- Sprint planning: When a team uses sprint-based delivery alongside continuous work, sprint management supports planning and tracking within the project management environment. Teams can choose an approach that suits each project.
- Progress visibility: When people need to understand project status without manually checking every task, built-in reporting presents progress in a more accessible way. This can support planning conversations and review meetings.
- Repeatable task handling: When teams repeatedly perform the same administrative actions, automation can reduce manual steps. For example, a workflow may update a task after a defined event.
- Fewer add-on dependencies: When essential project work relies on multiple plugins, built-in workflow and reporting capabilities may reduce the need for some add-ons. Teams can evaluate which extra integrations they still need.
- Deployment choice: When hosting requirements affect platform selection, ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments. Teams can choose an environment that fits their operational constraints.
- Consistent self-hosted capabilities: When a team needs to host its own environment, ONES.com offers full feature parity between its cloud and self-hosted versions. This gives teams flexibility without intentionally reducing the self-hosted feature set.
Application scenarios
A software team moving from Jira could assess ONES Project for Jira-compatible workflows, sprint management, custom fields, and reporting. It can compare the setup with its current board and identify which plugins remain necessary.
A team with strict hosting requirements could compare ONES.com’s On-Premise, Private Cloud, or Air-gapped deployments with its operational needs. It should also confirm which configuration is appropriate for its environment.
A growing organization can start with the free plan, which supports up to 30 seats, and evaluate whether the platform fits its teams. It can consider ONES Project for project management and add ONES Wiki separately if knowledge management is needed.
Common challenges when creating a Jira Kanban board
- The board shows too few tasks. Review the project selection or saved-filter criteria, then check whether permissions affect visibility. Test with a task you expect to see.
- Tasks appear in the wrong column. Check which Jira status each column includes. Move statuses to the correct column, then verify the result with a few sample tasks.
- The team can’t agree on when to move work. Define a simple entry and exit condition for each stage. For example, a task might enter “Review” only when implementation is complete.
- Work piles up in one stage. Look for a repeated blocker, unclear ownership, or a shortage of review capacity. A work-in-progress limit can make the bottleneck visible and prompt a practical conversation.
FAQs
Can I create a Kanban board in Jira without creating a new project?
Yes. You can usually create a board for an existing project, or create one from a saved filter that selects work from one or more projects. The exact options depend on your Jira setup and permissions.
If you choose a filter, check its criteria before relying on the board. A filter that excludes a status, issue type, or project can leave expected tasks off the board.
What is the difference between a Jira Kanban board and a Scrum board?
A Kanban board is designed to show work moving through a continuous workflow. Teams use columns to represent stages and can manage work without planning fixed-length sprints.
A Scrum board supports sprint-based work, including planning and tracking tasks in time-boxed iterations. Choose the board type that matches the way your team plans and delivers work.
Why are some Jira tasks missing from my board?
First, check whether the tasks belong to the project or saved filter connected to the board. Then review the filter criteria, status mapping, and permissions that control which work you can view.
If the task is included by the filter but still doesn’t appear, check whether its status is mapped to a board column. A Jira administrator can help investigate permission or configuration issues.
How many columns should a Kanban board have?
Use enough columns to show meaningful stages, without adding steps that the team cannot distinguish in practice. A small team may start with “To Do,” “In Progress,” and “Done.”
Add a stage such as “Review” or “Testing” when it reveals a real handoff or delay. If two columns mean nearly the same thing to the team, consider combining them.
Conclusion
To create a useful Jira Kanban board, choose the right project or filter, select Kanban, map statuses to clear columns, and verify that the expected work appears. Then share the board and adjust it as your team learns what helps.
A confusing board can hide delays and create more questions than it answers. Start with a workflow your team understands, keep the view focused, and review it regularly. That gives you a practical foundation for managing work as it moves from start to completion.