Kanban WIP limit per person in Jira: beyond column limits

Q: Where do I set column limits in Jira?

On company-managed boards, under Board settings → Layout → Columns → Column constraints. You can set a minimum, a maximum or both for each column.

By Kayabyte · Updated 1 November 2026

Short answer: Jira’s Kanban column constraints limit the number of cards in a column and colour the header when it’s exceeded; they don’t stop anyone and say nothing about how many cards one person holds. Assignee swimlanes or a JQL dashboard show work per person. A limit that holds without someone watching needs a check when the card moves, which takes a scripted validator or an app such as Personal WIP Limits: Work in Progress per Person for Jira.

A Kanban board with column limits looks like it limits work in progress. It limits the number of cards in a column. It says nothing about how many cards one person is holding. This guide covers the idea behind WIP limits, what Jira’s column limits do, how to see work per person, and what to do when you want a limit for each person.

The idea in short

Little’s law says that on average, cycle time equals work in progress divided by throughput. Wikipedia has the formula and its conditions. Throughput is how many items you finish per week. If it stays the same and you hold less work in progress, each item takes less time from start to finish.

An example: 20 items in progress and 4 finished a week means about 5 weeks per item on average. With 8 in progress and the same 4 a week, it’s about 2 weeks.

Two cautions:

The law describes averages in a steady system. It doesn’t promise any single item will be quick.
It says nothing about why throughput holds. The usual argument is that people who work on fewer things at once switch less. That’s a widely held view in Kanban practice, but it’s argued more than measured, so treat it as a rule of thumb.

Where does a person come in? Work in progress is the sum of what each person is holding. One person with six items and five people with one each can have the same board total. The team’s limit is respected and one person is stretched.

What Jira’s column limits do

In company-managed boards you set limits under Board settings → Layout → Columns → Column constraints. Atlassian describes them in Configure columns:

You choose to count work items, or work items excluding sub-tasks, and set a minimum, a maximum, or both for each column.
A column header turns red when the maximum is exceeded and yellow when the minimum isn’t met.
The count includes every work item in the column, also those hidden by a quick filter.

Atlassian’s page describes this as a visual indicator. People can still move work into a full column.

So column limits answer “is this stage getting crowded?” They don’t answer “is Sam doing too much?”.

Why column limits aren’t enough

They count the column, not the person. Three people can split a column limit of 6 as 4, 1 and 1.
They count one board. Someone on three teams’ boards can be under every column limit and still hold ten items.
They don’t stop anything. Red is a signal, and a busy week turns it into background.
A column holds several states. “In Progress” and “In Review” can be separate statuses in one column, so people can hold work in several places at once.

A per-person view with swimlanes

You can at least see who holds what. On company-managed boards, Configure swimlanes lists Assignees as a swimlane option: one lane per person, with unassigned work shown separately.

Open Board settings → Swimlanes.
Choose Assignees.
Look at the In Progress columns. A lane with a long run of cards is someone over their limit.

For a view across all boards, create a saved filter and use it in a dashboard gadget with Assignee as one axis:

statusCategory = "In Progress" AND assignee is not EMPTY ORDER BY assignee

It shows the problem. It doesn’t stop anyone, and it needs someone to look at it in the daily stand-up.

Make it a team agreement

Agree a number, for example 3 per person, and what counts: moving from To Do to In Progress, not from In Progress to In Review. Then decide what happens when someone is at the limit. In Kanban the answer is usually to help finish something instead of starting something. That works on teams that check the board together every day.

For a rule that holds without someone watching, the check has to run when the card moves. Jira’s built-in workflow validators can’t count how many work items a person already has in progress, so it takes a scripted validator or an app. The guide on how to set a WIP limit per person in Jira covers Automation and the workflow options in detail.

Personal WIP Limits: Work in Progress per Person for Jira

Personal WIP Limits: Work in Progress per Person for Jira is the app I make for this. It adds one workflow rule to the transitions that start work, and it works next to your column limits.

When the assignee is at their limit, Jira shows a message such as “Alex has reached the limit of 3 work items in progress” and the work item stays where it was.
One limit for everyone, counted across all projects or per project. Projects can have their own limit when counting per project, and groups such as on-call can be exempt.
Moves between In Progress statuses and unassigned work are never blocked. If the app can’t check, the move goes ahead.
An overview shows work in progress per person against the limit.
Everyone gets the same limit. Different limits for different people aren’t available in this version.
Limits are a guardrail, not a guarantee: two moves made in the same moment can both go through.

It’s on the Atlassian Marketplace.

FAQ

What does Little’s law say about work in progress? On average, cycle time equals work in progress divided by throughput. If throughput stays the same and you hold less work in progress, each item takes less time on average. It describes averages in a steady system, not any single item.

Where do I set column limits in Jira? On company-managed boards, under Board settings → Layout → Columns → Column constraints. You can set a minimum, a maximum or both for each column.

Do column limits count work hidden by a quick filter? Yes. The count includes every work item in the column, also those hidden by a quick filter.

Can Personal WIP Limits give different people different limits? Not in this version. Everyone gets the same limit; projects can have their own limit when counting per project, and groups such as on-call can be exempt.

Jira and Atlassian are trademarks of Atlassian. Kayabyte is an independent developer and is not affiliated with or endorsed by Atlassian.