Delete Issue: Jira action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Issue Key or ID issue_key	string	Required	The issue key (e.g. PROJ-123) or numeric ID
Delete Subtasks deleteSubtasks	options	Optional	Whether to delete subtasks. Required if issue has subtasks.

Sample request

{
  "issue_key": "e.g. PROJ-123",
  "deleteSubtasks": "{{trigger.deleteSubtasks}}"
}

Returns

{
  "success": true
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Delete Issue.

What does the Delete Issue action do in Jira?

Permanently deletes a Jira issue by key or ID. Irreversible; pass deleteSubtasks=true to also remove children. Most teams transition to a Cancelled status instead.

What inputs does Delete Issue require?

Required: Issue Key or ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Jira returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Delete Issue support batch operations?

Yes. Run Delete Issue inside a Loop node to process arrays. Tiny Command handles Jira's rate limits automatically so you don't have to throttle manually.

More actions