Browse this guide

Set WIP limits on a Jira board

A work-in-progress (WIP) limit is a team agreement about how much work should be active at once. Jira’s column limits provide a visual warning when the count crosses a threshold. They do not prevent someone from adding another card.

WIP limits

A board administrator can configure column constraints.

  1. Choose what the limit measures

    For a review bottleneck, start with the Review column. Agree whether the unit is parent work items or all work including subtasks.
  2. Open column constraints

    Go to Board settings → Layout → Columns. Choose work item count, with or without subtasks, in the column-constraint settings.
  3. Set a maximum

    Enter a maximum for Review. For example, a trial limit of 4 makes a fifth item a signal to discuss capacity. This is an example to test with your team, not a recommended universal limit.
  4. Check the count without filters

    Return to the board and compare the total with the threshold. Company-managed constraints count work hidden by quick filters too. Do not raise the limit because your personal filtered view looks sparse.

Good to know

A useful limit prompts a decision rather than simply changing a header color.

  • Do not move unfinished work into Done to reduce the count.
  • Decide how blocked work counts. Hiding blocked cards can conceal the very capacity problem a limit should reveal.
  • If multiple statuses share Review, discuss their combined work as one queue. Use the status-mapping guide to make that structure explicit.

FAQ

Does Jira enforce a hard WIP limit?
Native column constraints are visual warnings. They do not block transitions or cap the number of visible cards.
What number should we choose?
Use a small trial based on the team’s current capacity and the kind of work. Review waiting time and completion before changing it; there is no single correct number for every team.

Sources