ActionJiraUpdated September 2026

How do I list Jira sprints for a board?

Short answer: You can list sprints in Jira by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Jira List Sprints 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.

List Sprints 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
Board ID
boardId
stringRequiredBoard ID. Example: 1
State
state
optionsOptionalState. Options: All, Active, Closed, Future
Sample request
{
"boardId": "e.g. 1",
"state": "{{trigger.state}}"
}
Returns
{
"values": [
{
"id": 1,
"name": "Sprint 1",
"state": "active",
"endDate": "2026-04-14T23:59:59Z",
"startDate": "2026-04-01T00:00:00Z"
}
]
}

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

Triggered by

Apps that pair well as the trigger for List Sprints.

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

FAQ

Questions about List Sprints.

What does the List Sprints action do in Jira?
Lists all sprints for a Jira board with state (future, active, closed) and dates. Useful for sprint pickers and reporting.
What inputs does List Sprints require?
Required: Board 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 List Sprints support batch operations?
Run List Sprints 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

Other Jira actions.

List Sprints in Jira — start free