jira_delete
Delete Jira issues, comments, worklogs, attachments, or watchers using API endpoints. Specify the path and optional parameters to remove resources from your Jira projects.
Instructions
Delete Jira resources. Returns TOON format by default.
Output format: TOON (default) or JSON (outputFormat: "json")
Common operations:
Delete issue:
/rest/api/3/issue/{issueIdOrKey}Query param:deleteSubtasks=trueto delete subtasksDelete comment:
/rest/api/3/issue/{issueIdOrKey}/comment/{commentId}Delete worklog:
/rest/api/3/issue/{issueIdOrKey}/worklog/{worklogId}Delete attachment:
/rest/api/3/attachment/{attachmentId}Remove watcher:
/rest/api/3/issue/{issueIdOrKey}/watchersQuery param:accountId={accountId}
Note: Most DELETE endpoints return 204 No Content on success.
API reference: https://developer.atlassian.com/cloud/jira/platform/rest/v3/
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | The Jira API endpoint path (without base URL). Must start with "/". Examples: "/rest/api/3/project", "/rest/api/3/search/jql", "/rest/api/3/issue/{issueIdOrKey}" | |
| queryParams | No | Optional query parameters as key-value pairs. Examples: {"maxResults": "50", "startAt": "0", "jql": "project=PROJ", "fields": "summary,status"} | |
| jq | No | JMESPath expression to filter/transform the response. IMPORTANT: Always use this to extract only needed fields and reduce token costs. Examples: "issues[*].{key: key, summary: fields.summary}" (extract specific fields), "issues[0]" (first result), "issues[*].key" (keys only). See https://jmespath.org | |
| outputFormat | No | Output format: "toon" (default, 30-60% fewer tokens) or "json". TOON is optimized for LLMs with tabular arrays and minimal syntax. |