Jira - Get Issue
↩ Part of the Jira integration.
Description
Section titled “Description”Reads a single issue by its key (GET /issue/{key}) and passes the full Jira object to the next node. Use it to enrich a workflow with the current state of a ticket: status, assignee, priority, custom fields.
You can narrow the response with the fields parameter, which keeps payloads small and executions fast.
Configuration
Section titled “Configuration”| Field | Type | Required | Description |
|---|---|---|---|
credentials_id | credentials | Yes | Jira credential |
issue_key | text | Yes | Issue key (e.g. OPS-123) |
fields | text | No | Comma-separated fields to return (e.g. summary,status,assignee) |
issue_key accepts dynamic variables. fields is sent as-is as a query parameter.
Credentials
Section titled “Credentials”This module requires a Jira (Atlassian) credential:
| Field | Description |
|---|---|
base_url | Site URL, e.g. https://your-domain.atlassian.net |
email | Atlassian account email |
api_token | API token from id.atlassian.com |
Output
Section titled “Output”data is the issue object returned by Jira:
{ "id": "10042", "key": "OPS-123", "self": "https://your-domain.atlassian.net/rest/api/3/issue/10042", "fields": { "summary": "Checkout returns 500", "status": { "name": "In Progress", "statusCategory": { "key": "indeterminate" } }, "assignee": { "accountId": "5b10a2…", "displayName": "Ana Ruiz" }, "priority": { "name": "High" } }}Along with it, _meta:
{ "moduleVersion": "1.0.0", "success": true, "key": "OPS-123", "totalMs": 188 }Usage Example
Section titled “Usage Example”Full issue
Section titled “Full issue”{ "credentials_id": "jira_ops", "issue_key": "OPS-123"}Only the fields you need
Section titled “Only the fields you need”{ "credentials_id": "jira_ops", "issue_key": "{{data.ticket_key}}", "fields": "summary,status,assignee"}Downstream nodes then reference {{data.fields.status.name}} or {{data.fields.summary}}.
- The key is URL-encoded automatically, so keys with unusual characters are safe.
- A
404means the issue does not exist or the credential’s account cannot see it. This is not retried — check the key and the project permissions. - Rich-text fields such as
descriptioncome back in ADF (a JSON structure), not as a plain string.
Related Nodes
Section titled “Related Nodes”- Jira: Search issues — get many issues with JQL instead of one by key.
- Jira: Update issue — write back to the issue you just read.
- Jira: Transition issue — change its status.