Transition Issue
jira.transition_issue
ActionBusiness appsconnection required
Calls the Jira API POST /rest/api/3/issue/{key}/transitions.
Move a Jira issue to a new status by transition id or name.
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
3 fields, 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, e.g. PROJ-123. Supports {{ }}. | string | Yes | — | — | — |
transition_name Transition name, e.g. 'Done'. | string | No | — | — | — |
transition_id Transition id (used if name is blank). | string | No | — | — | — |
- At least one of transition_name, transition_id must be set.
Output
One shape.
issue
| Field | Type | Example |
|---|---|---|
ok | boolean | — |
key | string | — |
transition_id | string | — |
{
"key": "",
"ok": false,
"transition_id": ""
}See Transition Issue 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.