Link Issues
jira.link_issues
ActionBusiness appsconnection required
Calls the Jira Cloud REST API with the connection's email and API token.
Create a link of a named type between two Jira issues.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Username & password
- Providers
- Jira
- Secret shape
- {"email", "api_token"}
- Config it needs
- domain
- Resolved by
- config.connection_id, else node.connection_id
Configuration
4 fields, 3 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
link_type Link type name, e.g. 'Blocks' or 'Relates' — list them with jira.list_issue_link_types. | string | Yes | — | — | — |
inward_issue Key of the issue on the inward side of the link — for 'Blocks', the issue that is blocked. | string | Yes | — | — | — |
outward_issue Key of the issue on the outward side of the link — for 'Blocks', the issue that blocks. | string | Yes | — | — | — |
comment Optional comment to add with the link — plain text, or ADF as JSON. | string | No | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok True when Jira accepted the call. | boolean | — |
link_type The link type that was created. | string | — |
inward_issue The inward issue key. | string | — |
outward_issue The outward issue key. | string | — |
{
"inward_issue": "",
"link_type": "",
"ok": false,
"outward_issue": ""
}Notes
- Rich text takes plain text — one paragraph per line — or a full Atlassian Document Format document written as JSON. Jira Cloud v3 stores only ADF, so a plain string sent straight to the API is what makes a field render empty.
See Link Issues run in a workflow.
In a technical demo we add the Jira connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.