issue/get resource: issue

When to Use

• Status-gated workflow routing: Before transitioning an issue, call issue/get to read the current status. If it is already "Done", skip the transition. This prevents API errors from attempting invalid state changes.
• PR-to-issue context enrichment: When a GitHub pull request is opened with a Jira key in its title or branch name, fetch the full issue to extract the assignee, priority, and description — then include that context in the PR review notification sent to Slack.
• Escalation checks: A scheduled workflow runs every 15 minutes to fetch high-priority issues that have been "In Progress" for more than 4 hours without update, then sends a manager alert if the issue is still open past SLA.
• Integration data enrichment: A deployment pipeline records a Jira issue key. Before deploying, the pipeline fetches the issue to confirm it has status "Approved for Release". If not, the deployment is blocked and the issue creator is notified.
• Report generation: A weekly report workflow fetches each issue from a curated list, extracts summary, assignee, priority, and days open, then assembles a Notion database row or email attachment with the current state of each tracked item.

Configuration

Connection

Operation Fields

Sample Configuration

{
  "resource": "issue",
  "operation": "get",
  "Host": "https://acmecorp.atlassian.net",
  "Email": "automation@acmecorp.com",
  "ApiToken": "{{ $credentials.jiraApiToken }}",
  "IssueKey": "{{ $json.jiraIssueKey }}"
}

Validation Errors

Output Fields

Sample Output

{
  "status": "success",
  "issueId": "10482",
  "issueKey": "PROJ-123",
  "summary": "[P1 ALERT] Payment gateway timeout — checkout-service",
  "description": "Service: checkout-service\nEnv: production\n\nERROR: Connection timeout after 30s to payment-gw.internal:8443",
  "status_val": "In Progress",
  "priority": "Highest",
  "assignee": "Sarah Chen",
  "resource": "issue",
  "operation": "get"
}

Expression Reference

Node Policies & GuardRails

• Use issue/get for single known keys: When you have a specific issue key from a prior step, use issue/get. For unknown sets, use issue/getAll with JQL — it is more efficient than calling issue/get in a loop.
• Handle null fields gracefully: description and assignee may be null for issues created without these fields. Use null-coalescing expressions: {{ $output.getIssue.assignee ?? "Unassigned" }}.
• Status string comparison is case-sensitive: Jira status names are case-sensitive in expressions. Use exact casing from your project's workflow (e.g. "In Progress" not "in progress").
• API token in Credentials Manager: Never hard-code the API token. Reference it as {{ $credentials.jiraApiToken }}.

Workflow Examples

Example 1 — Status Gate Before Transition

Read current issue status before attempting a workflow transition to avoid invalid transition errors.

// Step 1: issue/get
{
  "resource": "issue",
  "operation": "get",
  "IssueKey": "{{ $json.issueKey }}"
}

// Step 2: IfCondition — gate on status
// Condition: {{ $output.getIssue.status_val }} !== "Done"

// Step 3 (if not done): issue/executeTransition
{
  "resource": "issue",
  "operation": "executeTransition",
  "IssueKey": "{{ $json.issueKey }}",
  "TransitionId": "{{ $json.transitionId }}"
}

Example 2 — Enrich PR Notification with Jira Context

GitHub webhook triggers on PR open → extract Jira key from branch name → fetch issue → post enriched Slack alert.

// Step 1: WebhookTrigger (GitHub PR opened)
// Step 2: Extract issue key from branch name (e.g. "feature/PROJ-123-payment-fix")
// Step 3: issue/get with extracted key
{
  "resource": "issue",
  "operation": "get",
  "IssueKey": "{{ $json.extractedKey }}"
}

// Step 4: Slack/postMessage
{
  "channel": "#engineering",
  "text": "PR opened: {{ $json.pr.title }}\n*Jira:* {{ $output.getIssue.summary }} ({{ $output.getIssue.status_val }})\n*Assignee:* {{ $output.getIssue.assignee }}\n*Priority:* {{ $output.getIssue.priority }}"
}