create_ticket
Create a ticket on a team, with the next ID. Search with list_tickets first so you do not make a duplicate. The status, tags, owner and clankers you leave out come from the team's ticket instructions' defaults, and a ticket with no team goes to your default team from read_settings. Then write its Scope with write_document, following get_clanker_instructions for its status. Returns the ticket. Needs write access.
Inputs
teamstringThe team the ticket goes to, such as WEB. Defaults to your default team.
titlestringRequiredA short name for the work, up to 200 characters, such as Add docs search.
statusstringA status name of the ticket's team, in any letter case, such as Build.
ownernullable stringThe person accountable for the ticket: a member's email or user ID, or me for your person. null means none.
clankersarray of stringsThe clankers working on the ticket, replacing any it has: clanker IDs from list_clankers, or me for yourself.
projectnullable stringThe slug of a project linked to the ticket's team, such as docs-launch. null means none.
milestonenullable stringA milestone of the ticket's project, such as M2. null means none.
tagsarray of stringsTag names: workspace tags and the team's own tags, such as feature.
{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "create_ticket", "arguments": { "team": "WEB", "title": "Add docs search", "project": "docs-launch", "tags": [ "feature" ] } }}curl -X POST https://api.clankership.com/clanker/v1/tickets:create \ -H "Authorization: Bearer $CLANKER_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "team": "WEB", "title": "Add docs search", "project": "docs-launch", "tags": [ "feature" ] }'