JiraSettings
| Setting | What it is |
|---|---|
| ConnectionRequired | The Jira connection the step signs in with. |
| Project keyRequired | The key in front of every issue number, for example ENG in ENG-142. The List projects node gives you the keys. |
| Issue typeRequired | The name as Jira shows it — Task, Bug, Story, Sub-task. The List issue types node gives you the names this project allows. |
| SummaryRequired | text |
| Description format | "text" or "adf" or "none" |
| Description | Jira stores rich text as a JSON document. A blank line starts a new paragraph and a single newline becomes a line break; nothing else is interpreted. |
| Description (ADF) | A full Atlassian Document Format document: { "type": "doc", "version": 1, "content": [ … ] }. |
| Assignee account id | Jira Cloud identifies people by account id, never by username or e-mail. The Find users node gives you one. |
| Reporter account id | text |
| Priority | The name as Jira shows it. Leave empty to use the project's default. |
| Labels | Comma-separated. A Jira label may not contain a space. |
| Due date | text |
| Parent issue key | For a sub-task, or for an issue under an epic on a team-managed project. |
| Components | Comma-separated names. |
| Fix versions | Comma-separated names. |
| Custom fields | Jira keys a custom field by its id — customfield_10034, never its title. The List fields node gives you the ids. Values are sent as written; a field that wants an object needs the escape below. |
| Extra fields (raw JSON) | Merged into the fields object verbatim, for a field whose value is an object or an array — { "customfield_10050": { "value": "Red" } }. Anything here wins over the fields above. |
Technical details
| Key | Value |
|---|---|
connection | texta connection id from `requires.connections` (provider `jira`) |
project | texta value from the vendor's own list |
issueType | texta value from the vendor's own list |
summary | text |
descriptionFormat | "text" or "adf" or "none", by default "text" |
description | textused when `descriptionFormat` is "text" |
descriptionAdf | object (any keys), by default {}used when `descriptionFormat` is "adf" |
assigneeAccountId | text |
reporterAccountId | text |
priority | text |
labels | text |
dueDate | text |
parent | text |
components | text |
fixVersions | text |
customFields | object of text, by default {} |
extraFields | object (any keys), by default {} |
Output
| Field | Type |
|---|---|
issueRefIssue key | string |
issueId | string |
issue | object |
issueUrlLink to the issue | string |
Sample output, and the expression for each field
- issue{}
- issueId"10042"
- issueRef"ENG-142"
- issueUrl"https://acme.atlassian.net/browse/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": {
"assigneeAccountId": "",
"components": "",
"connection": "<connection id>",
"customFields": {},
"description": "",
"descriptionAdf": {},
"descriptionFormat": "text",
"dueDate": "",
"extraFields": {},
"fixVersions": "",
"issueType": "<issue type>",
"labels": "",
"parent": "",
"priority": "",
"project": "<project key>",
"reporterAccountId": "",
"summary": "<summary>"
},
"label": "Create issue",
"type": "jira.createIssue",
"version": 1
}