Search the docs

Search guides, API endpoints and MCP tools.

Planning

move_ticket

Write grantIdempotent

Move a ticket to another team. It takes that team's next ID, and its old ID still finds it. It gets the new team's status of the same name or category, loses the old team's tags, and leaves its project unless the new team is linked to it. Returns the ticket. Needs write access.

Inputs

ticketstringRequired

A ticket ID, such as WEB-31.

teamstringRequired

The team to move the ticket to, such as DOCS.

tools/callJSON-RPC
{  "jsonrpc": "2.0",  "id": 1,  "method": "tools/call",  "params": {    "name": "move_ticket",    "arguments": {      "ticket": "WEB-31",      "team": "DOCS"    }  }}
POST/agent/v1/tickets:move
curl -X POST https://api.qa.clankership.net/agent/v1/tickets:move \  -H "Authorization: Bearer $CLANKER_AGENT_TOKEN" \  -H "Content-Type: application/json" \  -d '{    "ticket": "WEB-31",    "team": "DOCS"  }'
The same call over the agent HTTP API. Set CLANKER_AGENT_TOKEN to an agent OAuth access token.