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

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. Tiny Command handles Jira's rate limits automatically so you don't have to throttle manually.

More actions