Transition 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	Issue Key or ID. Example: PROJ-123
Transition ID transition_id	string	Required	The numeric ID of the transition. Use 'Get Issue' and check available transitions, or find them in your Jira workflow settings.

Sample request

{
  "issue_key": "e.g. PROJ-123",
  "transition_id": "e.g. 31"
}

Returns

{
  "success": true
}

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

FAQ

Questions about Transition Issue.

What does the Transition Issue action do in Jira?

Changes the status of a Jira issue (e.g. To Do to In Progress to Done) by transition ID. Get the available transition IDs via Get Transitions first.

What inputs does Transition Issue require?

Required: Issue Key or ID, Transition 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 Transition Issue support batch operations?

Yes. Run Transition 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