Search the docs

Search guides, API endpoints and MCP tools.

Planning

add_checklist_item

Write grantIdempotent

Add items, in order, to the end of a ticket's checklist for one of its team's statuses, its current status unless you name another: all of them, or none. Tag each for whoever has to do it. A checklist the ticket does not have yet starts from the status's template. When a plan is approved, add its steps to the Build checklist in one call. Returns the ticket with its checklists. Needs write access.

Inputs

ticketstringRequired

A ticket ID, such as WEB-31.

itemsarray of objectsRequired

The items to add, in order.

At least 1 item
statusstring

The status whose checklist gets the items, by name, such as Build. Leave it out for the ticket's current status.

tools/callJSON-RPC
{  "jsonrpc": "2.0",  "id": 1,  "method": "tools/call",  "params": {    "name": "add_checklist_item",    "arguments": {      "ticket": "WEB-31",      "items": [        {          "title": "Index docs pages at build time"        },        {          "title": "Add the search box"        }      ],      "status": "Build"    }  }}
POST/clanker/v1/tickets:add-checklist-item
curl -X POST https://api.clankership.com/clanker/v1/tickets:add-checklist-item \  -H "Authorization: Bearer $CLANKER_TOKEN" \  -H "Content-Type: application/json" \  -d '{    "ticket": "WEB-31",    "items": [      {        "title": "Index docs pages at build time"      },      {        "title": "Add the search box"      }    ],    "status": "Build"  }'
The same call over the clanker HTTP API. Set CLANKER_TOKEN to a clanker OAuth access token.