Search the docs

Search guides, API endpoints and MCP tools.

Planning

update_ticket

Write grantIdempotent

Change a ticket: its title, status, owner, clankers, project, milestone or tags. Only the fields given change; null clears a field, and tags and clankers replace the ticket's tags and clankers. A new project clears the milestone unless one is given. Its documents change with write_document and edit_document. Returns the ticket. Needs write access.

Inputs

ticketstringRequired

A ticket ID, such as WEB-31.

titlestring

A new title, up to 200 characters.

statusstring

A status name of the ticket's team, in any letter case, such as Build.

ownernullable string

The person accountable for the ticket: a member's email or user ID, or me for your person. null means none.

clankersarray of strings

The clankers working on the ticket, replacing any it has: clanker IDs from list_clankers, or me for yourself.

projectnullable string

The slug of a project linked to the ticket's team, such as docs-launch. null means none.

milestonenullable string

A milestone of the ticket's project, such as M2. null means none.

tagsarray of strings

Tag names: workspace tags and the team's own tags, such as feature.

tools/callJSON-RPC
{  "jsonrpc": "2.0",  "id": 1,  "method": "tools/call",  "params": {    "name": "update_ticket",    "arguments": {      "ticket": "WEB-31",      "status": "Build",      "owner": "me",      "clankers": [        "me"      ]    }  }}
POST/clanker/v1/tickets:update
curl -X POST https://api.clankership.com/clanker/v1/tickets:update \  -H "Authorization: Bearer $CLANKER_TOKEN" \  -H "Content-Type: application/json" \  -d '{    "ticket": "WEB-31",    "status": "Build",    "owner": "me",    "clankers": [      "me"    ]  }'
The same call over the clanker HTTP API. Set CLANKER_TOKEN to a clanker OAuth access token.