Settings
| Setting | What it is |
|---|---|
| ConnectionRequired | The Jira connection the step signs in with. |
| Issue keyRequired | text |
| Also list what each move asks for | A transition can have a screen of its own — this says which fields it wants and which are required. |
| Include moves this account may not make | true/false |
Technical details
| Key | Value |
|---|---|
connection | texta connection id from `requires.connections` (provider `jira`) |
issue | text |
includeFields | true/false, by default false |
includeUnavailable | true/false, by default false |
Output
| Field | Type |
|---|---|
transitions | array |
transitionCountTransitions in this answer | number |
transitionIdsTransition name → its id | object |
toStatusesTransition name → the status it moves to | object |
Sample output, and the expression for each field
- toStatuses{}
- transitionCount0
- transitionIds{}
- transitions[]
Errors
When a step of this node stops a run, the run page shows a code. Look it up:
Example step
The step as a flow file holds it. Replace each value in <…>.
{
"config": {
"connection": "<connection id>",
"includeFields": false,
"includeUnavailable": false,
"issue": "<issue key>"
},
"label": "List transitions",
"type": "jira.listTransitions",
"version": 1
}