Get Issue: Jira action · Tiny Command

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Issue Key or ID issue_key	string	Required	The issue key (e.g. PROJ-123) or numeric ID

Sample request

{
  "issue_key": "e.g. PROJ-123"
}

Returns

{
  "id": "10001",
  "key": "PROJ-123",
  "fields": {
    "status": {
      "name": "In Progress"
    },
    "created": "2025-01-01T00:00:00.000+0000",
    "summary": "Fix login redirect",
    "assignee": {
      "displayName": "John Doe"
    },
    "priority": {
      "name": "High"
    }
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Get Issue.

What does the Get Issue action do in Jira?

Retrieves a Jira issue by its key (ABC-123) or numeric ID with summary, description, status, assignee, comments, and custom fields. The standard read after a trigger fires with an ID.

What inputs does Get Issue require?

Required: Issue Key or ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Jira returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Get Issue support batch operations?

Yes. Run Get Issue inside a Loop node to process arrays. Tiny Command handles Jira's rate limits automatically so you don't have to throttle manually.

More actions