Atlassian Jira Kanban: A Step-by-Step Board Setup Guide
Struggling to spot stalled work? Set up an Atlassian Jira Kanban board step by step. Read now to build a clearer workflow.
A Jira Kanban board can make work easier to see and help your team manage tasks as they move toward completion. But a confusing board, mismatched statuses, or too much work in progress can create more questions than answers.
If your team has trouble spotting stalled work or deciding what to tackle next, the problem may be the board’s setup. But here's the truth: you don’t need a complicated workflow to get started. A few deliberate choices can make your board useful from day one.
This guide walks you through creating and configuring an Atlassian Jira Kanban board, from choosing a project to improving the workflow after launch. You’ll also see how to keep the board clear as your team’s work changes.
Set Up a Jira Kanban Board: Step by Step
To set up a Jira Kanban board, choose the project or work items it should show, create the board, then align its columns with your team’s actual workflow. Add work-in-progress limits where they help, and review the board regularly.
Choose a project or team workflow. Decide which work the board should track. A support team might use one project, while a product team may need a board that brings together several related projects.
Create the board. In Jira, open the board area and choose the option to create a Kanban board. Depending on your Jira edition and permissions, you may be able to create it from an existing project or from a saved filter.
Name the board and set its scope. Use a name your team can recognize, such as “Website Improvements” or “Customer Support Queue.” If the board uses a filter, make sure its criteria include the right projects, work types, and statuses.
Map statuses to columns. Match each board column to one or more workflow statuses. A simple setup could use “To Do,” “In Progress,” and “Done.” Add a separate review or testing column only if the team actually uses that stage.
Set work-in-progress limits. If your team often starts new tasks while existing ones remain unfinished, set a limit for the busy columns. For example, a team of five might try a limit of three active tasks, then adjust it after observing the flow.
Make work visible. Choose useful card details, such as the assignee, priority, or due date. Use swimlanes or quick filters only when they help people find relevant work faster.
Test the board with real tasks. Move a few items through the workflow and check whether their transitions appear as expected. Ask teammates to try common actions before relying on the board for daily planning.
Jira’s menus and available options can differ by edition, project type, and permissions. If an option is missing, check with your Jira administrator before changing the project’s workflow.

Choose the Right Project and Board Scope
A board is easiest to use when its scope reflects a real team or type of work. Before creating one, agree on what belongs there. For example, a marketing team might track campaign requests on one board rather than mixing them with unrelated infrastructure tasks.
You can build a board around a single project or use a saved filter to show work across projects. The second option can help a cross-functional team, such as a product group coordinating design, engineering, and quality checks. But it also means the filter needs regular attention.
Here's why: if the board omits relevant tasks, teammates may rely on side conversations to understand progress. If it includes everything, important work can disappear in the clutter. Start with a clear scope, then test it against a few real examples.
Configure Columns and Workflow States
Columns should describe meaningful stages of work, not every small action someone takes. A product team might use “Ready,” “In Progress,” “Review,” and “Done.” A small support team may need only “Open,” “Working,” and “Resolved.”
In Jira, columns represent the board’s view of progress, while workflow statuses determine an item’s state. Map the appropriate statuses to each column. If an item seems to skip a stage or remains in the wrong column, check the status mapping and the project’s transition rules.
Let me explain: adding columns does not automatically simplify the workflow. For instance, a “Waiting for Approval” column is useful when approval regularly blocks delivery. If the team rarely uses it, the extra stage may slow down updates without providing a clearer picture.
Use Work-in-Progress Limits Thoughtfully
Work-in-progress, or WIP, limits show how many items the team aims to keep in a column at one time. They can prompt a conversation when too many tasks are underway, rather than encouraging everyone to start something new.
Try a modest limit in a column where work commonly piles up. If a team of four regularly has seven items in review, a limit of three may encourage people to help clear reviews. Treat the limit as a signal to investigate, not a reason to hide work or block urgent exceptions.
Make the Board Useful for Daily Work
A well-configured board should answer practical questions quickly: What needs attention? Who owns this task? Where is work waiting? Add card details that help answer those questions, and remove details that teammates rarely use.
Swimlanes can group work by assignee, priority, or another relevant category. Quick filters can help people focus on a subset, such as high-priority tasks or items assigned to them. For example, a support team might use a quick filter for urgent requests during its daily check-in.
The best part? You can start with a basic view and add options only when people ask for them. Too many colors, filters, and swimlanes can make a board harder to scan, much like a crowded noticeboard makes key messages easy to miss.
Launch, Review, and Improve the Workflow
Introduce the board with a short walkthrough. Show teammates how to find their work, update statuses, and flag blocked tasks. Agree on what “Done” means so one person’s completed task does not remain unfinished in someone else’s view.
During the first few weeks, look for patterns rather than judging the board by one busy day. If several items wait in review, check whether reviewers have enough time. If tasks rarely move into “Ready,” the team may need clearer entry criteria.
You might be wondering: how often should you revise the board? Review it when the workflow changes or when the same bottleneck keeps appearing. A monthly check-in can work for a stable team; a team changing its process may need to review sooner.
ONES.com Solution for Project and Knowledge Management
Value proposition: ONES.com brings project management and knowledge management together on one platform. ONES Project is a Jira alternative for managing work, while ONES Wiki is a Confluence alternative for team knowledge; the products are sold separately.

Teams that need Jira-compatible workflows, on-premise deployment, or fewer add-ons can evaluate ONES Project alongside their existing Jira Kanban setup. Cloud and self-hosted versions have full feature parity, so teams can choose a deployment that fits their operating environment.
Core Capabilities
Complex workflow setup: Teams may struggle to represent their process clearly. ONES Project supports custom workflows and fields, helping teams organize work around their own stages and requirements.
Jira migration or compatibility needs: Rebuilding familiar processes can take effort. Jira-compatible workflows help teams carry over established ways of working while evaluating a Jira alternative.
Limited sprint planning: Teams balancing Kanban and sprint-based work may need more than a basic task board. Sprint management supports planning and tracking work across iterations.
Manual status tracking: Repetitive updates can take time. Automation can handle selected workflow actions, helping teams reduce routine steps and keep work moving.
Low visibility into progress: A board alone may not answer every planning question. Built-in reporting gives teams another way to review progress and workflow patterns.
Too many add-ons: Teams relying on several plugins may prefer more capabilities within the project management platform. ONES Project includes workflows, fields, reporting, sprint management, and automation.
Deployment restrictions: Some organizations need to control where their project management environment runs. ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployment options.
Separate project and knowledge needs: Teams may manage delivery and internal knowledge in different places. ONES Project and ONES Wiki address these needs within the ONES.com platform, and each is available separately.
Application Scenarios
A regulated organization may need project management in a restricted environment. It can evaluate ONES.com’s self-hosted or air-gapped deployment options while retaining access to the platform’s feature set.
A Jira team with plugin overhead may compare its existing setup with ONES Project. The team can assess whether built-in reporting, workflow customization, and automation meet its needs with fewer add-ons.
A cross-functional delivery team can use project management for work tracking and add ONES Wiki when it needs a separate knowledge management capability. This provides a way to manage delivery and team knowledge through products in the same platform.
Common Challenges with Jira Kanban Boards
Tasks Appear in the Wrong Column
Problem: A task has the right status in its workflow but appears under an unexpected board column. Solution: Review the board’s status-to-column mapping and test a transition. Confirm that every status used by the project has a clear place on the board.
The Board Feels Overloaded
Problem: Too many columns, card details, or swimlanes make it hard to spot urgent work. Solution: Remove options that don’t help the team make a decision. Keep stages tied to meaningful handoffs, and retain card details people use during planning.
Work Stalls in One Stage
Problem: Items collect in review or testing, but the team keeps starting new tasks. Solution: Use a WIP limit to make the bottleneck visible. Then discuss practical causes, such as reviewer availability, unclear acceptance criteria, or a handoff that needs attention.
Some Work Is Missing from the Board
Problem: Teammates can’t find relevant tasks, especially on boards spanning several projects. Solution: Check the board’s filter criteria and access permissions. Test the board with representative tasks and confirm the intended team can see them.
FAQs About Jira Kanban Boards
How do I create a Kanban board in Jira?
Open Jira’s board area and choose the option to create a Kanban board. Depending on your edition and permissions, you can create one for a project or use a saved filter. Name the board, confirm its scope, then configure its columns and status mappings. Test it with a few real tasks before introducing it to the team.
What columns should a Jira Kanban board have?
Choose columns that reflect the stages your team uses to move work forward. A simple board might have “To Do,” “In Progress,” and “Done.” Add stages such as “Review” or “Testing” only when they represent a meaningful handoff or help the team identify where work is waiting.
Can a Jira Kanban board include work from multiple projects?
Yes. A board can use a saved filter to show work from multiple projects, if your Jira setup and permissions allow it. This can help a cross-functional team see related tasks together. Check the filter carefully so it includes relevant work without pulling in unrelated tasks.
Does a Kanban board need work-in-progress limits?
No, but WIP limits can help teams notice when too many tasks are active at once. Start with a limit in a column where work regularly piles up. Review how it affects the team, then adjust it to fit actual capacity. The goal is to prompt useful discussion, not to prevent sensible exceptions.
Conclusion: Keep the Board Clear and Actionable
A useful Jira Kanban board starts with a clear scope, columns that match the workflow, and status mappings that work in practice. Add WIP limits and visual options when they help the team spot problems or choose the next task.
If your current board feels confusing, you don’t have to rebuild everything at once. Test one improvement with real work, ask teammates what changed, and refine the setup as the workflow evolves. That small, deliberate approach can make progress easier to see and stalled work easier to address.