A status is a step in your workflow — New, In Progress, Review, Done — and a status collection is an ordered set of them that a board uses as its columns. Different boards can use different collections: a simple three-column collection for a support board, a longer one with Code Review and QA for an engineering board.
A WIP limit (work-in-progress limit) is a cap on how many items a status should hold at once. It is the Kanban idea that finishing beats starting: if In Progress is capped at 5 and already holds 5, the team swarms to finish something before pulling more. DevStride makes the limit visible rather than enforcing it.
Configure Settings → Data Model → Item Statuses. The page heading reads Manage Item Statuses. It needs the Manage work types permission (default Owner and Admin roles). Statuses for subtasks are set separately, on Subtask Statuses directly below it in the menu.
Click New, enter a Status Name and pick a Status Color. Two statuses are Reserved by System and cannot be renamed or deleted:
Everything else is User Defined: In Progress (created for you), Approved, Review, Pending Release, and so on. A status is shared across collections, so renaming it or changing its colour applies everywhere. A user-defined status can also be terminal, as Shipped or Cancelled are; see Terminal statuses.
Click New to create a Status Collection, then drag statuses from the pool into it; drag within to order the columns, drag out to remove. In a long list, hold the item on the band at the top or bottom edge and the list scrolls straight away. Each status row in a collection has two more settings:
Removing a status from a collection asks you to confirm; any item in that status on a board using the collection moves to the collection's default status.
Status collections are applied to boards, not to teams or item types. Open the board (or cycle) in Plan Delivery and choose the collection in its settings; see Boards and WIP limiters. A new organization has one collection, Default, with New → In Progress → Done.
When an item moves to a board, team or item type whose collection does not include its current status, DevStride picks the closest status in the new collection:

When a board column holds more items than its limit, the column header turns the warning colour and shows WIP Limit (n). Nothing is blocked: people can still move items in. The signal is the point. Use the Cumulative Flow and Cycle Time reports to see whether the limit is being respected and whether it is helping.
Deleting a status first moves every item still in it to the first valid status in the item's collection, so nothing is left pointing at a status that no longer exists. Two rules apply:
Not all finished work was completed. A request can be cancelled, withdrawn or declined; a feature can be shipped under its own name rather than moved to Done. A terminal status is one where an item's lifecycle is complete: Done, Cancelled, Rejected, Shipped and the like. Any user-defined status can be made terminal, with an outcome:
Open the status (Edit in the pool), switch on Terminal status, and choose Completed or Not completed. The pool and every collection then show the outcome as a small badge beside the status name. New cannot be terminal, and Done is always terminal as Completed.
Saving applies the change to the items already in that status, in the background. The save message tells you how many items are being updated:
Effort Points and Time Estimation
Turn effort points on per item type and choose the point format, and define the three-point time-estimate ranges (optimistic, likely, pessimistic) each item type offers.
Subtask Statuses
Add your own subtask statuses, such as Cancelled or Blocked, beside New, In Progress and Done, and choose which ones count as finished.