Start free
ActionJiraUpdated June 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.

FieldTypeRequiredDescription
Sprint ID
sprintId
stringRequiredSprint ID
Max Results
maxResults
numberOptionalMax 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.

Gmail → Jira
1 Gmail triggers
Slack → Jira
13 Slack triggers
Google Sheets → Jira
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 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 Sprint Issues support batch operations?
Yes. Run Get Sprint Issues inside a Loop node to process arrays. TinyCommand handles Jira's rate limits automatically so you don't have to throttle manually.
More actions

Other Jira actions.

Action
Add Comment
Adds a comment to an existing Jira issue with optional visibility restriction (role or group). Used for automation activity logs, AI summary notes, or external system pings.
Action
Add Watcher
Adds a user as a watcher on a Jira issue so they receive notifications on updates. Used to auto-loop in interested parties (PMs, designers, support).
Action
Assign Issue
Assigns a Jira issue to a user (by accountId) or unassigns it. The standard routing action for AI-driven triage or rotating on-call assignment.
Action
Create Issue
Creates a new issue (story, task, bug, epic, etc.) in a Jira project with summary, description, type, assignee, priority, labels, components, and custom fields. Standard write for converting external alerts into tracked work.
Action
Delete Issue
Permanently deletes a Jira issue by key or ID. Irreversible; pass deleteSubtasks=true to also remove children. Most teams transition to a Cancelled status instead.
Action
Get Issue
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.
Get Sprint Issues in Jira — start free