JiraSettings
| Setting | What it is |
|---|---|
| ConnectionRequired | The Jira connection the step signs in with. |
| Issue keyRequired | text |
| Fields to fetch | Jira returns nothing you do not ask for. *all returns everything and is slow on a big issue. |
| Expand | text |
| Name custom fields by their key | Off, Jira names them by id — customfield_10034. |
| Also give the description as plain text | Jira stores a description as a JSON document. This adds the words beside it, so you do not have to walk the tree. |
Technical details
| Key | Value |
|---|---|
connection | texta connection id from `requires.connections` (provider `jira`) |
issue | text |
fields | text, by default "summary,status,assignee,priority,labels,duedate" |
expand | text |
fieldsByKeys | true/false, by default false |
plainTextDescription | true/false, by default true |
Output
| Field | Type |
|---|---|
issue | object |
issueRefIssue key | string |
issueId | string |
issueUrlLink to the issue | string |
fields | object |
descriptionTextDescription in words | string |
status | string |
Sample output, and the expression for each field
- descriptionText"It jams"
- fields{}
- issue{}
- issueId"10042"
- issueRef"ENG-142"
- issueUrl"https://acme.atlassian.net/browse/ENG-142"
- status"In Progress"
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>",
"expand": "",
"fields": "summary,status,assignee,priority,labels,duedate",
"fieldsByKeys": false,
"issue": "<issue key>",
"plainTextDescription": true
},
"label": "Get issue",
"type": "jira.getIssue",
"version": 1
}