Delete issue with the Jira API

Deletes an issue. An issue with subtasks is only deleted with deleteSubtasks set to true, which deletes them too. Needs the Delete issues permission in the project. The response is empty, status 204.

Identifier
jira_delete_issue

The request

POST https://connect.reportei.com/api/tools/jira_delete_issue/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "issueIdOrKey": "<issueIdOrKey>"
  }
}

Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.

Parameters

ParameterTypeRequiredDescription
issueIdOrKeystringYesIssue id or key, for example KEY-123, from Search issues.
deleteSubtasksstringNotrue also deletes the subtasks of the issue.Values: true, false

Supported connections

Your customer connects their Jira account once, with one of the modes below. The same connection serves every tool of the toolkit.

Username and password

Your customer enters the app credentials on a Connect screen, or your system sends them with POST /api/customer-toolkits, with no screen.

When connecting, your customer also enters {site}: the address of their account on the app's API.

The response

On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.

Ready for AI agents

This tool's input is a JSON Schema, available at GET /api/tools/jira_delete_issue. It becomes your agent's tool definition with no conversion.

Other Jira tools

See all 13 tools

Toolkits in the same category

See all 100 toolkits

See Connect applied to your product.

Try it for 15 days with no card, or walk our team through your use case.