List Sprints: Jira action

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
Board ID boardId	string	Required	Board ID. Example: 1
State state	options	Optional	State. 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.

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 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 List Sprints support batch operations?

Yes. Run List Sprints 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