task_done
Destructive
Finishes the work on a taken task (shared team data): outcome, result, message and usage in one call. Outcomes: done (the work is done or accepted and the task moves on), return (sent back with a required message, including bugs in work returning to testing), wait (the part is done, the task waits in the queue), close. The server makes the transition, closes the worklog and calculates the cost of the work from the difference of the start and end snapshots.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"outcome": "<outcome>",
"run": "<run>"
},
"name": "task_done"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ID | No | Task ID; preferred over key. | |
| key | No | Task number without #, if the ID is unknown. | |
| run | Yes | Session counters accumulated since its start, as at the start of the work, at the end of the same session; limits - subscription limits at the end (window to utilization 0-1 and resetsAt in ISO 8601), accuracy 0-1 - counters accuracy, 1 by default. | |
| gist | No | Gist: one or two plain-text sentences "problem → solution", up to 300 characters, without Markdown, links or task keys, in the language of the workspace data; updated if the solution changed. | |
| result | No | Result: in work - the whole result field (Markdown in the language of the workspace data, HTML is rejected; replaces the whole field), the tester's "QA verification" block is kept by the server; in testing - only that block, placed by the server at the end of the field; not accepted at approval and review. | |
| message | No | Message to the task chat: required for a return (what to fix); otherwise only what people need to know. | |
| outcome | Yes | One of the outcomes returned when the task was taken. | |
| moduleIDs | No | Full new list of modules actually touched. | |
| attachments | No | File IDs (fid) of uploaded files, up to 5, attached to the message. | |
| closeReason | No | Closing reason, required for close: resolved, notDoing, notReproducible, notBug or duplicate; the explanation goes in the message. | |
| componentIDs | No | Full new list of components actually touched. |