List Transitions
jira.list_transitions
ActionBusiness appsconnection required
Calls the Jira Cloud REST API with the connection's email and API token.
List the workflow transitions currently available on a Jira issue.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Username & password
- Providers
- Jira
- Secret shape
- {"email", "api_token"}
- Config it needs
- domain
- Resolved by
- config.connection_id, else node.connection_id
Configuration
1 field, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
issue_key Issue key or numeric id, e.g. PROJ-123. Supports {{ }}. | string | Yes | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
transitions[].id The transition id to pass to jira.transition_issue. | string | — |
transitions[].name The transition's name, e.g. 'Done'. | string | — |
transitions[].to The status the transition moves the issue to. | string | — |
count How many items this call returned. | number | — |
{
"count": 0,
"transitions": [
{
"id": "",
"name": "",
"to": ""
}
]
}Notes
- The list depends on the issue's current status and on your permissions, so it differs from issue to issue.
See List Transitions run in a workflow.
In a technical demo we add the Jira connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.