Get Issue
jira.get_issue
ActionBusiness appsconnection required
Calls the Jira Cloud REST API with the connection's email and API token.
Read one Jira issue, with the fields and expansions you ask for.
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
3 fields, 1 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 |
|---|---|---|---|---|---|
issue_key Issue key or numeric id, e.g. PROJ-123. Supports {{ }}. | string | Yes | — | — | — |
fields Comma-separated field ids or names to return, e.g. 'summary,status,assignee'. Leave blank to return every field. | string | No | — | — | — |
expand Comma-separated expansions, e.g. 'renderedFields,changelog,names'. | string | No | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
id The issue's numeric id, as a string. | string | — |
key The issue key. | string | PROJ-123 |
fields The issue's fields, exactly as Jira returned them. | object | — |
url Browser URL for the issue. | string | — |
{
"fields": {},
"id": "",
"key": "PROJ-123",
"url": ""
}Notes
- Custom fields are keyed by id, not label: 'customfield_10011'. Run jira.list_fields once to map a field's name to its id.
See Get Issue 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.