ActionJiraUpdated September 2026

How do I list all issues in a Jira sprint?

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

Get Sprint Issues in Jira — start free All 17 Jira actions

Get Sprint Issues 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
Sprint ID sprintId	string	Required	Sprint ID
Max Results maxResults	number	Optional	Max Results

Sample request

{
  "sprintId": "{{trigger.sprintId}}",
  "maxResults": "{{trigger.maxResults}}"
}

Returns

{
  "total": 5,
  "issues": [
    {
      "id": "10001",
      "key": "PROJ-1",
      "fields": {
        "status": {
          "name": "In Progress"
        },
        "summary": "Fix login bug"
      }
    }
  ]
}

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

Triggered by

Apps that pair well as the trigger for Get Sprint Issues.

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 Sprint Issues.

What does the Get Sprint Issues action do in Jira?

Returns all issues in a Jira sprint. Used for stand-up dashboards, sprint reviews, or burndown reporting outside Jira.

What inputs does Get Sprint Issues require?

Required: Sprint 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 Sprint Issues support batch operations?

Run Get Sprint Issues 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