Can Jira stop one person from having too many work items?

By Kayabyte · Updated 18 November 2026

Short answer: Not with a built-in setting. Jira has no cap on how many work items one person can be assigned or can have in progress; board column limits count cards in a column, not people, and they only warn. You can see who holds too much with JQL and a dashboard, or react after the fact with Automation. To stop a move into In Progress when the assignee is already at their limit, Personal WIP Limits: Work in Progress per Person for Jira is an app I make.

Disclosure: I make Personal WIP Limits. The built-in options come first, and nothing before the app section needs an app.

“Assigned” and “in progress” are two different things in Jira, and a limit can sit on either. This guide separates them, says what Jira does for each, and where each option stops.

What Jira does today

Option 1: see it with JQL

This finds the work items each person is currently working on:

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

Put it in a dashboard gadget with Assignee as one axis, or save it as a filter and subscribe to it. For everything assigned and not done, use statusCategory != Done instead. Where it stops: it shows the problem, it doesn’t prevent it, and it only reflects the moment someone looks.

Option 2: an Automation rule after the assignment

A rule can trigger when a work item is assigned, count the assignee’s open work with a lookup (a JQL such as assignee = {{assignee.accountId}} AND statusCategory != Done), and then comment, notify the lead, or clear the assignee when the count is over your number. Where it stops:

Option 3: a scripted check on the transition

A workflow validator written with a scripting app can count the assignee’s work and refuse the move. It’s the closest native-style answer to a hard limit, and it needs a scripting app and someone who can maintain the script. Jira’s built-in validators can’t count work items.

Decide before you pick a tool

Personal WIP Limits: Work in Progress per Person for Jira

Personal WIP Limits puts the limit on starting work. You add its workflow rule to the transitions that start work, in company-managed or team-managed workflows.

Limits: it checks when work starts, not when work is assigned. Changing the assignee of a work item that is already In Progress, or creating a work item straight into In Progress, isn’t checked. Someone can still be assigned a long list of To Do items; the limit applies when they try to start another.

It’s on the Atlassian Marketplace. For the Kanban view, see Kanban WIP limit per person in Jira, and for the full set of options, How to set a WIP limit per person in Jira.

Not a Jira admin? Send this to yours

Only an admin can install apps. Copy this note and send it to yours:

Could we try Personal WIP Limits? Give each person a WIP limit in Jira. At the limit, Jira stops new work from starting and says why. Works in company-managed and team-managed projects. It is on the Atlassian Marketplace and built on Atlassian Forge, and it makes no calls outside Atlassian. Free for up to 10 users. Listing: https://go.kayabyte.dev/atl/wip-limits?s=site-ask-jira-limit-issues-assigned-per-person

FAQ

Can Jira limit how many work items one person is assigned? No. There is no setting for a maximum per assignee. You can see the count with JQL and a dashboard, or react after an assignment with Automation.

Do board column limits limit what one person holds? No. They count cards in a column and only colour the header when it’s exceeded.

Does Personal WIP Limits stop me from assigning work to someone who is full? No. It checks when a work item moves into an In Progress status, and the work item stays where it is when the assignee is at their limit.

Can some people be exempt? Yes. You can exempt groups, for example an on-call or support group.

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