Create a Kanban Board in Jira: A Quick Step-by-Step Guide
Need a clearer view of team work? Create a Kanban board in Jira with this quick guide. Read now to set up columns and track tasks.
A Jira board can make work easier to see, but a new board can feel confusing when you’re unsure where to begin. Pick the wrong project or filter, and your team may see incomplete work, confusing columns, or issues that don’t belong.
That friction can slow stand-ups and make it harder to spot blocked tasks. The good news is that you can create a Kanban board in Jira in a few minutes, then adjust it as your workflow becomes clearer. I’ll walk you through the setup, explain how columns connect to statuses, and show you practical ways to keep the board useful. But here’s the truth: creating the board is the easy part. A well-matched workflow is what helps your team use it every day.
How to Create a Kanban Board in Jira
To create a Jira Kanban board, choose a project or saved filter, create a board, then configure its columns to match your team’s workflow. You’ll need the relevant Jira permissions to create or manage boards.
- Check your project and permissions. Decide which Jira project should appear on the board. If you can’t create boards or change board settings, ask a Jira administrator to grant the required access.
- Open the board creation option. In Jira, go to
Boards and choose View all boards, then select Create board. Menu names and locations can vary slightly between Jira versions.
- Choose a Kanban board. Select the Kanban option when Jira asks what kind of board you want. Kanban boards display work as cards moving through workflow columns.
- Choose what the board displays. Create the board from a project for a straightforward setup. Choose a saved filter if you need to include issues from several projects or apply more specific criteria.
- Name the board and finish setup. Use a name your team can recognize, such as “Mobile App Support.” If you selected a saved filter, confirm that the people who need the board can view that filter.
- Review columns and statuses. Open the board settings and check that each workflow status appears in the right column. For example, map “Selected for Development” and “In Progress” to an active-work column if that reflects your process.
- Test the board with real work. Open a few issues, move one through the workflow, and confirm that the board shows the expected results. Invite your team to check access before relying on the board in meetings.
Here’s why: a board is a view of Jira issues, not a separate workflow. Its project or filter determines which issues appear, while its column settings determine how you see their progress.

Choose a Project or a Saved Filter
A project-based board is often the simplest choice when one team works in one Jira project. For example, a support team can create a board that displays issues from its service project without building extra filtering rules.
A saved-filter board can suit a team that works across projects. A release team might use a filter to display issues tagged for a specific release, even when those issues belong to different projects.
Let me explain: the board only shows issues that match its project or filter settings. If an expected issue is missing, check the filter criteria and viewing permissions before changing the board layout.
Make Columns Match Your Workflow
Kanban columns give the team a visual path from new work to completed work. A small product team might use “To Do,” “In Progress,” “Review,” and “Done,” while a service team may need “Waiting for Customer” or “Escalated.”
Columns are connected to Jira workflow statuses. If an issue has a status that isn’t mapped to a visible column, it may appear in an unexpected place or be absent from the board.
The best part? You can adjust column names and status mappings as the team learns what it needs. Keep the stages understandable; five useful columns are generally easier to discuss than ten narrowly defined ones.
Decide How to Handle Backlog and Work in Progress
Some Kanban boards include a backlog area for work that is not ready to move into the active workflow. This helps a team separate possible future tasks from work it has committed to doing now.
Work-in-progress limits can also help the team notice when too many tasks are active at once. For example, if the review column regularly fills with six issues, a limit may prompt teammates to review existing work before starting another task.
You might be wondering: should every team set limits immediately? Try the board for a short period first, then use actual bottlenecks to decide whether limits or a backlog change would help.

Configure Board Settings for Daily Use
Board settings can make it easier to focus on relevant work. Depending on your Jira setup, you may be able to configure swimlanes, quick filters, card details, and work-in-progress limits.
For example, a quick filter for “Assigned to me” can help each person find their tasks during a stand-up. A swimlane grouped by assignee may help a small team spot uneven workloads at a glance.
Keep the initial setup practical. Add a setting when it solves a real problem, such as needing to separate urgent support requests from routine work, rather than adding options the team rarely uses.
Keep the Board Accurate as Work Changes
A board stays useful when people update issues as work progresses. If a task is waiting for review, move it to the review status instead of leaving it in “In Progress.” That small habit makes the board a more reliable view of current work.
Set a brief routine for reviewing stale issues, blocked work, and tasks that no longer belong on the board. For instance, a team might check these items during its weekly planning session and update the workflow when a recurring handoff causes confusion.
Here’s the practical test: can a teammate understand what is happening by looking at the board? If not, review the statuses, issue details, and team habits before adding more columns.
ONES.com is a unified platform for project management and knowledge management, powered by ONES Assistant. ONES Project provides project management, while ONES Wiki provides knowledge management; the products are sold separately.

For teams looking for a Jira alternative, ONES Project offers Jira-compatible workflows and project management features. It may suit teams that want project controls with fewer separate plugins, including organizations that need self-hosted deployment options.
Core Capabilities
- Need a familiar workflow? ONES Project supports Jira-compatible workflows, helping teams carry over established work patterns.
- Want to see progress clearly? Built-in reporting gives teams a way to review project progress without relying on a separate reporting plugin.
- Have a process that needs tailoring? Custom workflows and fields let teams adapt issue tracking to their working practices.
- Plan work in sprints? Sprint management supports teams that use iterative planning and delivery.
- Want to reduce repetitive steps? Automation can handle selected routine actions, helping teams spend less time on manual updates.
- Need project and knowledge capabilities? ONES.com brings project management and knowledge management into one platform, with ONES Project and ONES Wiki available separately.
- Need a self-hosted environment? ONES.com offers On-Premise, Private Cloud, and Air-gapped deployments, as well as Cloud.
- Need a low-cost way to evaluate it? The free plan supports up to 30 seats, giving a team room to try the platform before choosing a broader rollout.
ONES.com offers four deployment options: Cloud, On-Premise, Private Cloud, and Air-gapped. Its cloud and self-hosted versions have full feature parity, so deployment choice does not require giving up feature access.
Application Scenarios
A software team moving away from Jira may use ONES Project to manage tasks, sprints, custom fields, and reporting in a Jira-compatible workflow. It can evaluate the setup with a small team before planning a wider transition.
An organization with restricted network requirements may consider an Air-gapped or other self-hosted deployment. A team that also needs knowledge management can assess ONES Wiki separately from ONES Project.
Common Challenges When Setting Up a Jira Kanban Board
- The board is missing issues. Check whether the project or saved filter includes the expected issues. Also confirm that the people viewing the board have permission to see the project and filter.
- Issues appear in the wrong column. Review the status-to-column mapping. A status can exist in the workflow but still need to be assigned to the intended board column.
- The board feels crowded. Narrow the board’s scope with an appropriate project or filter, and remove columns that don’t represent meaningful steps in the team’s process.
- Team members forget to update cards. Agree on when to move issues and who updates them during handoffs. A short review during stand-ups can reveal outdated statuses before they become a pattern.
- People can’t access the board. Check board sharing, project permissions, and access to any saved filter. Ask a Jira administrator for help if your account cannot change those settings.
Frequently Asked Questions
Can I create a Kanban board from an existing Jira project?
Yes. When creating a board, choose the option to create it from a project and select the relevant Jira project. This is a straightforward setup when the board should show work from one project. After creation, check the column and status mappings to make sure issues appear in the right stages.
What is the difference between a Jira project and a board?
A Jira project organizes issues and related work, while a board displays selected issues in a visual workflow. A board can show work from a project, or it can use a saved filter to include issues from multiple projects. That distinction matters when a team expects to see work that belongs to more than one project.
Can one Jira project have more than one Kanban board?
Yes. A project can be viewed through multiple boards when each board serves a different purpose. For example, a development team could use one board for general work and another board with a filter for urgent defects. Make sure each board’s scope and audience are clear to avoid confusion.
Why can’t I see an issue on my Kanban board?
First, check whether the issue matches the board’s project or saved filter. Then check the issue’s status mapping and your access to the project and filter. If the issue still does not appear, ask a Jira administrator to review the board configuration and permissions.
Can I change the columns after creating the board?
Yes. Board settings let you adjust columns and map workflow statuses to them. You can make changes when a team adds a review stage, renames a handoff, or finds that a status is appearing in the wrong place. Before changing a shared board, let the team know how the update affects its workflow.
Conclusion
Creating a Jira Kanban board starts with choosing the right project or filter, then mapping workflow statuses to clear columns. Test it with real issues, confirm access, and refine the layout as your team learns what helps it see work.
If the board feels confusing, focus on the workflow and issue scope before adding more settings. A carefully configured Jira board can make everyday work easier to follow, while teams considering a Jira alternative can also evaluate ONES Project for project management needs.