Kanban boards in Jira: how to set one up and when it feels heavy

A Jira kanban board comes with every kanban software space. Create a space from the Kanban template and the board is the first thing that opens, with four default columns: Backlog, Selected for Development, In Progress and Done. Everything after that is configuration. Columns are mapped to workflow statuses, work in progress limits are called column constraints, and both live under Board settings, then Layout, then Columns. The Free plan covers up to 10 users, so a small team can run a full kanban board without paying.

This guide walks through that setup using the screen names in Atlassian's current Jira Cloud documentation, checked on October 8, 2026. It then covers what the board does well once it is running, and the specific points where small teams start to find Jira heavy.

What a Jira kanban board is made of

A Jira board is not a container of work. It is a view of work items that live in a space. That distinction explains most of the confusion new users run into.

Four pieces decide what appears on the board and where:

• The board filter. A saved query decides which work items the board shows. If a work item does not match the filter, it does not appear, no matter what its status is. In Board settings, the Details page shows the filter query.
• Columns. Each column is mapped to one or more workflow statuses. A work item appears in the column its status is mapped to.
• Unmapped statuses. Any status not mapped to a column is hidden from both the board and the backlog. Atlassian's documentation calls this out directly, and it is the most common reason a work item "disappears".
• The rightmost column. Jira treats only work items in the rightmost column as complete. Statuses such as Done, Canceled or Won't do need to be mapped there, or reports will count them as unfinished.

Columns also carry a color that follows their position. The leftmost column is always gray for new work, the rightmost is always green for finished work, and any columns in between are blue for work in progress. Those colors show up elsewhere in Jira, including in gadgets, so moving a column changes how its work is reported.

Two kinds of space exist, and the setup screens differ between them. Team-managed spaces are set up and maintained by anyone on the team and have simpler configuration. Company-managed spaces are configured by Jira admins through shared schemes and screens, which lets an organization standardize workflows across many spaces. To check which one a space is, select More actions (•••) next to the space name in the header or sidebar; the space type is shown at the bottom of that menu.

What the Jira plans cover for a kanban team

Kanban boards are not a paid feature. The Jira pricing page, checked on October 8, 2026, lists backlog, list, board, timeline, calendar and summary views on the Free plan. The differences between plans are about scale, automation and administration.

	Free	Standard	Premium
Price per user per month	$0	$7.91	$14.54
User limit	10 users	100,000 users per site	100,000 users per site
Storage	2 GB	250 GB	Unlimited
Automation	150 steps per subscription per month	400 steps per user per month	750 steps per user per month
Email notifications	100 per day	Unlimited	Unlimited
Dependency management	Single project	Single project	Cross-project

The dollar figures are the US prices published in the pricing page's own structured data. The page also offers annual billing, which it says saves up to 17 percent, and calculates a total once a team size is entered. Enterprise is billed annually and quoted through sales.

For a kanban team, two rows matter more than the price. The 10 user limit on Free is a hard ceiling for the whole site, not per board. The automation allowance on Free is shared across the subscription, so a few rules that move cards or post comments on every transition can use it up in a busy month. Standard also adds user roles and permissions and external collaboration, which matter as soon as people outside the team need to see the board.

Setting up the board, step by step

The steps below follow Atlassian's Jira Cloud documentation for company-managed boards. Team-managed boards with the simplified workflow allow most of the same changes directly on the board, which is noted where it applies.

1. Create the space from the Kanban template

Create a new space and choose the Kanban template. The board opens with Backlog, Selected for Development, In Progress and Done.

2. Open the column settings

1. Next to the board's name in the sidebar, select More actions (•••), then Board settings.
2. Expand the rest of the sidebar menu by selecting Layout.
3. Select Columns.

Only a space administrator or a board administrator can change these settings.

3. Shape the columns

Under Map statuses to columns:

• To add a column, select Add (+) to the right of the columns, enter a name, choose a category, then select Add column. With the simplified workflow, a matching status is created automatically.
• To rename a column, select its name and edit it.
• To move a column, drag it by its top edge.
• To delete a column, select Delete. Its statuses move to the Unmapped statuses panel.

Then check the Unmapped statuses panel. Anything left there will be invisible on the board.

4. Set column constraints

Under Column constraints, choose Work item count or Work item count, excluding subtasks, then enter a minimum or maximum under each column name. When a maximum is exceeded, the column header turns red. When a minimum is not met, it turns yellow.

On a team-managed board with the simplified workflow, the same limit can be set by right-clicking a column name, or hovering and selecting More actions, then Set column limit.

5. Decide whether to enable the kanban backlog

In the same Columns screen, a kanban backlog panel appears under Map statuses to columns. Dragging an existing status onto it turns on a separate Backlog view. This is covered in the next section.

WIP limits, the kanban backlog and quick filters

Three features do most of the work once the board is live, and each has a detail that is easy to miss.

Column constraints warn, they do not block. Atlassian's documentation is explicit that the constraint values do not affect how many work items are displayed. A team can still drag a sixth card into a column limited to five. The header turns red and that is all. Constraints also count every work item in the column, including those hidden by a quick filter, so a filtered view can look under the limit while the column is over it. A team that wants the limit respected has to agree on what happens when the header turns red, for example that nobody pulls new work until something moves right.

The kanban backlog moves planning off the board. Without it, the first column becomes a long list that pushes the active work out of view. With it enabled, the Backlog view shows two sections, Backlog and Selected for Development, and work is dragged from one to the other when the team is ready for it. Two conditions control what appears there: the work item must match the board filter, and its status must map to the kanban backlog column or the next column on the board. If every status is mapped to the first board column, the Backlog section stays empty. The backlog also supports splitting a large work item into several. Right-click it and select Split work item, which is only possible from the backlog and not from the board.

Quick filters replace second boards. A common early mistake is creating a separate board for each person or each type of work. Quick filters, configured in Board settings, let the same board show only one assignee, one label or one epic with a click. Swimlanes then group rows on the board, for example an expedite lane for urgent work above everything else.

Reading the board with the built-in reports

Jira includes reports for kanban boards, and they answer questions a board alone cannot.

The Cumulative Flow Diagram is the one to open first. To view it, go to the space, choose the board, select Reports, then Cumulative Flow Diagram. Each colored band is a column on the board, plotted over time. A band that keeps getting wider is a queue growing in that column, which usually marks the bottleneck. Refine report narrows the data, and the date range can be changed at the top of the chart.

Two details from the documentation shape how to read it. The diagram only includes work items that match the board's saved filter. And it relies on column mapping: work is To Do when its status maps to the leftmost column and Done when it maps to the rightmost one. A board with Canceled mapped to a middle column will show cancelled work as permanently in progress.

The Control Chart shows how long work items take to move through the board. It is the answer to "how long does a typical request take from start to finish", which is the number stakeholders actually want from a kanban team.

A practical rhythm is to look at the Cumulative Flow Diagram once a week and the Control Chart once a month. The first catches a growing queue early. The second shows whether changes to the process are making work flow faster.

Where Jira starts to feel heavy for small teams

None of the following are defects. They are the cost of a tool built to scale to very large organizations, and they show up most clearly in teams of five to twenty people.

Configuration needs an administrator. Columns, statuses and constraints can only be changed by space or board admins. In company-managed spaces, workflows and screens are Jira admin territory, and a change to a shared scheme affects every space that uses it. In a small team, that usually means one person becomes the board's caretaker.

The vocabulary is a barrier for non-developers. Statuses, workflows, schemes, filters, JQL and epics are all needed to understand why a card is or is not on the board. Marketing, operations and client-facing staff often stop at that point.

Dates are a separate view. Timeline and calendar views exist, including on Free, but they sit beside the board rather than on it. Teams that plan around deadlines move between views to see the same work.

Conversation tends to happen elsewhere. Comments live on each work item, but day-to-day discussion often stays in a separate chat tool, which means decisions are split between two places.

The free ceiling is 10 users per site. An eleventh person, including someone from another department who only needs to move a card occasionally, puts the whole site on a paid plan.

For engineering teams that already use Jira for issues and releases, these costs are usually worth paying, because the board connects to everything else. For a small mixed team whose main need is moving cards across columns, a lighter kanban board tool may fit better. Some project management tools put kanban, Gantt, calendar and chat on every plan and limit only the number of people and boards. The comparison overview sets several of these side by side, and the features page shows which board types are available without configuration.

What to change first

On an existing Jira kanban board, open Board settings, then Columns, and empty the Unmapped statuses panel, then make sure every finished status sits in the rightmost column. Turn on column constraints for the In Progress column and agree as a team on what happens when it turns red. If the setup work itself is the problem, compare it with Pinateca, which includes kanban and Gantt boards on its free plan for up to five people and ten boards.

Q1. Is a Jira kanban board free?

Yes. The Jira Free plan includes board, backlog, list, timeline, calendar and summary views for up to 10 users per site, with 2 GB of storage. Paid plans add more users, more automation, storage and admin controls.

Q2. How do you add a column to a Jira kanban board?

Next to the board's name, select More actions (•••), then Board settings, then Layout, then Columns. Select Add (+), name the column, choose its category and select Add column. Only space or board administrators can do this.

Q3. Why is a work item missing from the Jira kanban board?

The two most common causes are that its status is not mapped to any column, or that it does not match the board filter. Check the Unmapped statuses panel in the Columns settings and the filter query on the Details page of Board settings.

Q4. Does Jira stop people from exceeding a WIP limit?

No. Column constraints change the column header to red when the maximum is exceeded and yellow when the minimum is not met, but they do not prevent cards from being moved. The limit works only if the team agrees how to respond to it.

Q5. What is the difference between the kanban backlog and the first board column?

Without the kanban backlog, upcoming work sits in the first column of the board. Enabling the kanban backlog moves it to a separate Backlog view with Backlog and Selected for Development sections, so the board shows only work the team has chosen to start.