Statuses and workflow
Columns belong to one board#
Every board is created with the same three — Backlog, In progress, Done — and from that moment they are that board's own. Two boards in the same workspace can have entirely different workflows.
Configuring the columns#
Needs the owner, admin, or member role, on a board you can reach.
- Add a column — up to 100 characters, appended after the existing ones.
- Rename a column — also sets a colour swatch.
- Reorder columns — drag the grip, or arrow keys.
- Delete a column — a board must keep at least one, and a column holding tickets cannot go until they are moved.
- Choose which column means done — see below.
- Gate a column — entry requirements decide what a ticket must carry before it is allowed in, see Boards.
What "complete" means#
Exactly one column per board is flagged as the completion column. The flag does two things:
- The tick shortcut sends a ticket to the completion column in one click.
- Sprint carry-over — tickets in the completion column stay behind when a sprint rolls over; everything else moves to the new board.
Columns you add yourself are never marked complete, but the flag can be moved with Set as completing column — a board never has two.
Moving a ticket#
Three gestures do the same thing: drag the card, change the Status dropdown, or use a hover shortcut. Two people moving the same ticket at once is resolved by the ticket's version — one write wins, the other is told the ticket changed underneath it.
Column names in the API#
Anywhere the API takes a status_uuid, it also takes a column name as
status, matched case-insensitively:
curl -X POST https://api.laver.app/tasks/11111111-2222-4333-8444-555555555555/move \
-H "Authorization: Bearer laver_..." \
-H "Content-Type: application/json" \
-d '{"version": 7, "status": "In progress"}'Send status or status_uuid, never both. See
Tickets by API and
Concurrency and polling.