Move an issue's card to another board column (status) and/or reorder it among the other cards, like dragging it (needs edit access). status is the target column (default: the issue's current column, i.e. reorder only). Ordering: after is the key of the issue that should sit directly above the card, before the key of the one directly below; both must be issues of the same project in the target column (a neighbour in another column is an error). Pass both for an exact slot between two cards; with only one, the card is placed a step past that neighbour and may not end up directly adjacent if other cards follow it. With neither, the card goes to the top of the column. after and before must differ. Optional expect {status}: the column you last saw the card in; if it is elsewhere now nothing is moved and the answer says where it is.
afterstringoptionalKey of the issue that should come right before (above) this one in the column (optional)beforestringoptionalKey of the issue that should come right after (below) this one in the column (optional)confirm_open_criteriaboolean | string[]optionalConfirm open acceptance criteria / definition of done items when the move is to a done status and the project's done_gate is warn: the ids of the open items (the refusal lists them; they must be all of the ones open now), or true for people (agents must send the ids). Under done_gate block nothing confirms it: check the items first.expectobjectoptionalThe status you last read. If the issue is in another status now, nothing is written and the answer names the current one.keystringrequiredIssue key to movestatusstringoptionalTarget column: a status key or name from list_statuses (default: the issue's current column)
Returns
abovestringoptionalbelowstringoptionalfromstringoptionalThe status key it was moved from, when the column changedkeystringrequiredmovedbooleanrequiredtrue when the issue changed column, false when it was only reorderedparent_readyarrayoptionalstatusstringrequiredThe status key (column) the issue is in now
- 2026-10-03 — New optional expect {status}: the column you last saw the card in. If it is elsewhere now nothing is moved and the answer says where it is.
- 2026-10-04 — The answer gains parent_ready [{key,title,type,children,status}]: when the call moved the last open child of a story or epic to done, that parent is listed (suggested done status in status). Nothing is changed for it.
- 2026-10-03 — New optional confirm_open_criteria: with done_gate warn, a move to a done status with open AC / DoD items is refused, listing them, until you send their ids (people may send true). done_gate block always refuses.
- 2026-10-03 — Also answers structuredContent (see outputSchema); a failed call adds structuredContent.error. Text unchanged. Details: /docs/mcp, "Structured results and errors".
- 2026-10-04 — Claude Code 2.1.288+ (clientInfo claude-code): the text of a successful answer is itself up to 512 bytes, else "Result in structuredContent (N bytes)."; structuredContent and errors are unchanged. See /docs/mcp.