Docs
Sign in

Search the docs

Search guides, API endpoints and MCP tools.

Planning

update_ticket_status

Write grantIdempotent

Rename a status, or make a Backlog status the one new tickets get. A new name follows into saved views. Returns the status. Needs write access, and your person must 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.

namestring

A new name, up to 40 characters, such as Triage.

defaultboolean

Make it the status new tickets get. Only a Backlog status can be.

Always true
tools/callJSON-RPC
{  "jsonrpc": "2.0",  "id": 1,  "method": "tools/call",  "params": {    "name": "update_ticket_status",    "arguments": {      "status": "Backlog",      "team": "WEB",      "name": "Triage"    }  }}
POST/clanker/v1/ticket-statuses:update
curl -X POST https://api.clankership.com/clanker/v1/ticket-statuses:update \  -H "Authorization: Bearer $CLANKER_TOKEN" \  -H "Content-Type: application/json" \  -d '{    "status": "Backlog",    "team": "WEB",    "name": "Triage"  }'
The same call over the clanker HTTP API. Set CLANKER_TOKEN to a clanker OAuth access token.
Nextreorder_ticket_status