How to set a WIP limit per person in Jira

By Kayabyte · Updated 1 November 2026

Short answer: Not with Jira’s built-in settings. Board column limits count every work item in a column on one board and only show a warning, so they don’t limit what one person holds. You can see work in progress per person with JQL and a dashboard, or warn with Automation after the move; to stop work from starting when the assignee is at their limit you need a scripted workflow validator or an app such as Personal WIP Limits: Work in Progress per Person for Jira.

Board column limits stop a column from filling up. They don’t stop one person from holding most of it. If you want “nobody has more than 3 things in progress”, this guide shows what Jira Cloud can do on its own, step by step, and where each option stops. For the flow-theory side (Little’s law, and why limits per column are not enough), see Kanban WIP limit per person in Jira.

Column limits: what they do and don’t do

In a board’s settings, under Columns, you can set a minimum and maximum number of work items per column. Jira then colours the column when it goes over.

The limit counts every work item in the column, whoever it’s assigned to.
It’s a warning. People can still move work into a full column.
It counts one board. Someone who works on three teams’ boards can be under every column limit and still have ten things in progress.

So column limits help a team see a bottleneck. They don’t give each person a limit.

See who is over: a filter and a dashboard

You can at least see who has too much in progress.

Create a filter with this JQL and save it, for example as “In progress by person”:
```
statusCategory = "In Progress" AND assignee is not EMPTY ORDER BY assignee
```
Add a Filter results or Two dimensional filter statistics gadget to a dashboard, using that filter, with Assignee as one axis.
Each person’s count is the number of work items they have in progress.

This shows the problem. Nobody is stopped, and someone has to look at it.

React after the fact: Jira Automation

Automation can warn when someone goes over their limit.

Trigger: Work item transitioned, to your In Progress statuses.
Action: Lookup work items with JQL such as assignee = {{issue.assignee.accountId}} AND statusCategory = "In Progress".
Condition: {{lookupIssues.size}} greater than your limit.
Action: add a comment, notify the team lead, or transition the work item back.

The catch: Automation runs after the move. The work item has already started, people get notifications about a move that is then undone, and the count can be off if two moves happen at the same moment. It’s a nudge, not a limit.

Prefer a script for the counting? atlassian-admin-scripts has a jira-wip-per-person script that lists who is over a limit and can run on a schedule. It’s free, MIT-licensed and uses the public REST API. It only reports and doesn’t stop anyone from starting work, and it reflects the moment you run it.

Stop the move: a workflow rule

To stop a work item from starting when its assignee is at their limit, the check has to run on the transition itself, before the move happens. Jira’s built-in validators can’t count how many work items someone already has in progress, so this needs a scripted validator or an app.

Decide these first, whichever you use:

Across all projects or per project. One limit for everything a person does, or a limit per project for people who split their time on purpose.
What counts as starting work. Moving from To Do into In Progress should count. Moving from In Progress to In Review should not.
Who is exempt. On-call or support rotations often need to pick up urgent work regardless.
What happens if the check fails. A limit that blocks people when Jira is slow does more harm than good. Let the move go ahead.

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 a workflow rule you put on the transitions that start work, in company-managed and team-managed workflows.

When the assignee is at their limit, Jira shows “Alex has reached the limit of 3 work items in progress” and the work item stays where it is.
Count across all projects or per project, give projects their own limit or switch them off, and exempt groups.
Moves between In Progress statuses and unassigned work are never blocked. If the app can’t check, the move goes ahead.
It stores only its settings and makes no calls outside Atlassian.

It’s on the Atlassian Marketplace.

FAQ

Do Jira column limits stop people from moving work into a full column? No. Jira colours the column when it goes over, but people can still move work into it.

Can Jira Automation enforce a per-person WIP limit? It can comment, notify or move the work item back, but it runs after the move. The work has already started, so it’s a nudge, not a limit.

What JQL shows work in progress per person? statusCategory = "In Progress" AND assignee is not EMPTY ORDER BY assignee, used in a dashboard gadget with Assignee as one axis.

Does Personal WIP Limits block moves between In Progress statuses? No. Moves between In Progress statuses and unassigned work are never blocked, and if the app can’t check, the move goes ahead.

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