Move an item to the next state
The complaint request has been triaged and someone is starting on it. Drag Handle complaints in one place instead of three inboxes from Triage into In Progress: the board writes the same state change the work item form would write, and everyone else sees it at their next refresh.
Before you start
- A board over a saved flat query, showing today rather than an As of snapshot, which is read-only.
- Permission to edit the item. The board writes as the signed-in user and grants no extra access.
A filter may stay on. With cards hidden, a drop into another column lands by the rule in Order a column by priority: directly above the visible card below the slot, after any hidden cards between, and a drop into a column that shows no cards keeps the card's place in the order.
Steps
- In your project navigation open Boards and select AnyKanban, then open the board.
- Leave Filter by keyword and the filter dropdowns as they are, or narrow the board to the cards you are working with.
- Press and hold on the card Handle complaints in one place instead of three inboxes and start moving the pointer. The drag begins after about 4 px, so a click on the card's title still just opens the work item.
- Move over the In Progress column. The card lifts out of Triage, a gap opens exactly where it will land, and the column you are over is outlined.
- Release the card over that gap.
What you should see
The card is in In Progress and its state row reads In Progress. Both column counts change at once, before the server has answered, and the write follows and confirms it. If it cannot be applied, the card and both counts go back to what the server says, and a message names the reason.
On the demo board In Progress carries a WIP limit of 4 and already holds four requests, so the counter now reads 5/4 in red. Nothing was blocked: the limit is a signal, not a gate.
Notes
Columns your process rules would reject for you and for this item are dimmed while you drag and carry the tooltip Transition restricted by process rules; the preview never enters one, and releasing the card on it cancels the whole drag. A rule that merely requires a field is deliberately not treated as a restriction: that column stays normal, the drop is attempted, and a rejection snaps the card back with the server's own message, which you can then satisfy on the work item form.