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.
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 |
{"boardId": "e.g. 1","state": "{{trigger.state}}"}
{"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.
Any of these apps can fire this action as part of a workflow.