Plan Delivery: Boards

Boards and WIP Limiters

Set a work-in-progress limit per status so a board column turns red when the team takes on too much — what the limit does, what it doesn't, and how to set one.

What a WIP limiter does

A WIP (work-in-progress) limit is the most items a status should hold at once. You set it per status inside a status collection. On any board using that collection, a Card-view column whose item count goes over the limit turns red and shows a WIP LIMIT (n) pill, where n is the limit.

That is all it does. It is a warning, not a gate:

Column turns red whenthe column holds more items than the limit (a column exactly at the limit is not flagged).
Dropping another card into a red columnstill works. Nothing blocks, no confirmation, no toast.
Counteditems on this board in that status, as currently loaded. Other boards sharing the status collection are not counted.
Shown inCard view only — including collapsed columns. Table and 2D views do not show WIP state.
Enforced by the server or automationsNo. There are no WIP triggers or conditions.

Set a WIP limit

You need the organization-settings capability (default Admin).

  1. Open Configure Settings → Data Model → Item Statuses.
  2. In 2 - Group into Collections, open the collection your boards use.
  3. In the WIP Limit column, enter a number for each status that needs one (1–2 in the image). Leave the field empty (shown as -) for no limit. The change saves on its own.

  • Only your own statuses can take a limit. The system statuses New and Done cannot.
  • A limit belongs to the status within that collection. The same status can have a different limit in another collection.
  • Every board on the collection gets the limit at once — perpetual boards and all current and future cycles.

The full statuses page: Item Statuses.

Working with a red column

The signal is deliberately soft so an emergency can still be pulled in. When a column goes red:

  • finish or hand off something in that status before starting more;
  • if it is red every sprint, the limit is wrong or the stage is understaffed — change one of them;
  • if you need a hard stop, agree the rule as a team; DevStride will not enforce it for you.

See the warning in context in Track and move work with board views.