JiraSettings
| Setting | What it is |
|---|---|
| ConnectionRequired | The Jira connection the step signs in with. |
| Issue keyRequired | text |
| Assign to | Nobody is only possible when the Jira admin allows unassigned issues; the default hands it to whoever the project names. |
| Account id | Jira Cloud identifies a person by account id, never by username or e-mail. The Find users node gives you one. |
Technical details
| Key | Value |
|---|---|
connection | texta connection id from `requires.connections` (provider `jira`) |
issue | text |
assignTo | "accountId" or "unassigned" or "default", by default "accountId" |
accountId | textused when `assignTo` is "accountId" |
Output
| Field | Type |
|---|---|
issueRefIssue key | string |
assignedJira accepted the change | boolean |
accountIdWho it went to | string |
Sample output, and the expression for each field
- accountId"5b10a2"
- assignedtrue
- issueRef"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": {
"accountId": "",
"assignTo": "accountId",
"connection": "<connection id>",
"issue": "<issue key>"
},
"label": "Assign issue",
"type": "jira.assignIssue",
"version": 1
}