JiraSettings
| Setting | What it is |
|---|---|
| ConnectionRequired | The Jira connection the step signs in with. |
| RelationshipRequired | With the type Blocks, the OUTWARD issue blocks the INWARD one. Jira's own link dropdown shows both wordings. |
| That issueRequired | The one on the receiving end — it is blocked, cloned or duplicated. |
| This issueRequired | The one the relationship starts from — it blocks, clones or duplicates. |
| Comment | Added to the issue as part of the same call. |
Technical details
| Key | Value |
|---|---|
connection | texta connection id from `requires.connections` (provider `jira`) |
linkType | text |
inwardIssue | text |
outwardIssue | text |
comment | text |
Output
| Field | Type |
|---|---|
linkedJira created the link | boolean |
linkTypeRelationship | string |
inwardIssueThat issue | string |
outwardIssueThis issue | string |
Sample output, and the expression for each field
- inwardIssue"ENG-99"
- linkType"Blocks"
- linkedtrue
- outwardIssue"ENG-142"
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>",
"inwardIssue": "<that issue>",
"linkType": "<relationship>",
"outwardIssue": "<this issue>"
},
"label": "Link issues",
"type": "jira.linkIssues",
"version": 1
}