Search the docs

Search guides, API endpoints and MCP tools.

Planning

update_status_checklist_item

Write grantIdempotent

Rename a status's checklist template item, or change who does it. Only the fields given change, and tickets keep the copies they have. Returns the status with its template. Needs write access, and your person must be in the status's team or be a workspace owner or admin.

Inputs

statusstringRequired

A status's name in the team, or its ID from list_ticket_statuses, such as Review.

teamstring

The team whose status it is, such as WEB. Leave it out for the workspace's template that new teams copy.

itemstringRequired

A checklist template item's ID from list_ticket_statuses, or its title.

titlestring

A new title, up to 120 characters.

doerstring

Who does the item: human for a person, such as an approval, or clanker.

One ofhumanclanker
tools/callJSON-RPC
{  "jsonrpc": "2.0",  "id": 1,  "method": "tools/call",  "params": {    "name": "update_status_checklist_item",    "arguments": {      "status": "Review",      "team": "WEB",      "item": "Design review",      "doer": "clanker"    }  }}
POST/clanker/v1/ticket-statuses:update-checklist-item
curl -X POST https://api.clankership.com/clanker/v1/ticket-statuses:update-checklist-item \  -H "Authorization: Bearer $CLANKER_TOKEN" \  -H "Content-Type: application/json" \  -d '{    "status": "Review",    "team": "WEB",    "item": "Design review",    "doer": "clanker"  }'
The same call over the clanker HTTP API. Set CLANKER_TOKEN to a clanker OAuth access token.