Get Transitions: 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 issue_key	string	Required	Issue Key. Example: PROJ-123

Sample request

{
  "issue_key": "e.g. PROJ-123"
}

Returns

{
  "transitions": [
    {
      "id": "11",
      "name": "To Do"
    },
    {
      "id": "21",
      "name": "In Progress"
    },
    {
      "id": "31",
      "name": "Done"
    }
  ]
}

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

FAQ

Questions about Get Transitions.

What does the Get Transitions action do in Jira?

Returns the available status transitions for an issue based on the workflow it's on. Required before calling Transition Issue, since you pass a transition ID, not a status name.

What inputs does Get Transitions require?

Required: Issue Key. 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 Get Transitions support batch operations?

Yes. Run Get Transitions 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