Skip to content

Jira - Get Issue

↩ Part of the Jira integration.

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.

FieldTypeRequiredDescription
credentials_idcredentialsYesJira credential
issue_keytextYesIssue key (e.g. OPS-123)
fieldstextNoComma-separated fields to return (e.g. summary,status,assignee)

issue_key accepts dynamic variables. fields is sent as-is as a query parameter.

This module requires a Jira (Atlassian) credential:

FieldDescription
base_urlSite URL, e.g. https://your-domain.atlassian.net
emailAtlassian account email
api_tokenAPI token from id.atlassian.com

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 }
{
"credentials_id": "jira_ops",
"issue_key": "OPS-123"
}
{
"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 404 means 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 description come back in ADF (a JSON structure), not as a plain string.