JiraSettings
| Setting | What it is |
|---|---|
| ConnectionRequired | The Jira connection the step signs in with. |
| Issue keyRequired | text |
| Name the move by | A Jira status is not written directly: you name a transition, and which transitions exist depends on the workflow and on where the issue is now. A name costs one extra read and survives a workflow edit; an id does not. |
| MoveRequired | The List transitions node shows both the names and the ids. |
| Comment | Added as part of the same move, so the change and its reason are one event. |
| Resolution | Many workflows require a resolution on the move to Done — give its name, for example Done or Won't Do. |
| Fields the move asks for | Keyed by field id — the List transitions node names them per move. |
| Extra fields (raw JSON) | For a field whose value is an object — { "customfield_10050": { "value": "Red" } }. |
Technical details
| Key | Value |
|---|---|
connection | texta connection id from `requires.connections` (provider `jira`) |
issue | text |
transitionBy | "name" or "id", by default "name" |
transition | text |
comment | text |
resolution | text |
fields | object of text, by default {} |
extraFields | object (any keys), by default {} |
Output
| Field | Type |
|---|---|
issueRefIssue key | string |
transitionId | string |
transitionName | string |
toStatusThe status it moved to | string |
Sample output, and the expression for each field
- issueRef"ENG-142"
- toStatus"Done"
- transitionId"41"
- transitionName"Done"
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": {
"comment": "",
"connection": "<connection id>",
"extraFields": {},
"fields": {},
"issue": "<issue key>",
"resolution": "",
"transition": "<move>",
"transitionBy": "name"
},
"label": "Move issue",
"type": "jira.transitionIssue",
"version": 1
}