Delete an issue (requires version) — its subtasks are deleted with it (D130 (6))
delete_issueDelete an issue (requires version) — its subtasks are deleted with it (D130 (6)).
Deleting cannot be undone from MCP. Pass the version from get_issue. Only delete when the user asked for it. Deleting an issue deletes its subtasks with it (a Sales & Billing deal takes its installments) — say so before deleting a parent.
WRITE: version = from your latest read (get_issue, list_comments, list_sprints, get_doc, read_file). 409 version_conflict (details.current, details.current_version): re-read, re-apply your change, retry — never overwrite blindly; when the changes disagree, ask the user.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"project_key": "<project_key>",
"issue_key": "<issue_key>",
"version": "<version>"
},
"name": "delete_issue"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| reason | No | Spec D144: why you make this change (≤ 200 characters). Optional, but give it when you act as an agent account — it is shown in the agent's run log. board-mcp records it; the service accepts and ignores it. | |
| version | Yes | Version of the file you read. Required on every delete (spec principle 7). | |
| issue_key | Yes | Issue key `{PROJECT}-{n}`, e.g. `KJ-101`. | |
| project_key | Yes | Project key, e.g. `KJ`. 2–10 chars, uppercase letters and digits, starts with a letter. |