Update Ticket
update_ticketUpdate a ticket in the markdown issue tracker: claim, resolve, or drop it, adjust dependency edges, add a comment, set triage, or check off acceptance criteria.
Instructions
Change one Ticket. Lifecycle: claim, resolve with a one-line gist, or drop with a reason — at most one of those per call. Graph: replace the Edges, refused if they close a cycle. Annotations: triage role, a comment, ticking acceptance criteria; these touch no part of the graph. Any of the three groups may accompany the others or stand alone.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Ticket id, or the <effort>#<order> handle of a Legacy Ticket. | |
| drop | No | Close the Ticket as work ruled out of scope. | |
| root | No | Workspace directory. Defaults to the session workspace. | |
| tick | No | Acceptance criteria to check off, matched on their text. Wrapped criteria match both as get_tickets returns them and re-joined onto one line. All references resolve before anything is written — one unmatched name fails the whole call and leaves the file untouched. | |
| claim | No | Take the Ticket. Fails if another holder already has it. | |
| status | No | Not settable directly — use claim, resolve, or drop. Named here to say so. | |
| triage | No | Set the triage role. A separate field from status; neither touches the other. | |
| comment | No | Append to the comment log, stored exactly as written. | |
| resolve | No | Close the Ticket as a step on the route. | |
| blocked_by | No | Replace the Edges outright, each a plain Ticket id resolved repo-wide. An empty list clears them. A cycle is refused. |