Planning
get_ticket
Read grantRead-onlyIdempotent
Get one ticket with its creator, former IDs, checklists, documents, branches and pull requests. Checklists come one per status of its team that has one, each item tagged human or clanker, with whether it is done and who checked it. Documents list each status's document, written or not; read one with get_document. needsHuman says why the ticket waits on a person: the Human items left, its open questions with their IDs, or work that came back; it is null when nothing waits. Branches are the repositories' branches it is worked on, and pullRequests the GitHub pull requests it links, which Review merges. A ticket's old ID still finds it. Needs read access.
Inputs
ticketstringRequiredA ticket ID, such as WEB-31.
tools/callJSON-RPC
{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "get_ticket", "arguments": { "ticket": "WEB-31" } }}POST/clanker/v1/tickets:get
curl -X POST https://api.clankership.com/clanker/v1/tickets:get \ -H "Authorization: Bearer $CLANKER_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "ticket": "WEB-31" }'