ActionJiraUpdated September 2026

How do I fetch a Jira issue by key or ID?

Short answer: You can get issue in Jira by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Jira Get Issue action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Get Issue in Jira — start free All 17 Jira actions

Get Issue in Jira — start free

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.

Triggered by

Apps that pair well as the trigger for Get Issue.

Any of these apps can fire this action as part of a workflow.

2 Google Sheets triggers

HubSpot → Jira

18 HubSpot triggers

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 run history shows the failed step with its input and the error message Jira returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Get Issue support batch operations?

Run Get Issue inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Jira's rate limits.

More actions