sprint-fetcher

sprint-fetcher

Fetches all issues in the current active sprint for the configured board. Handles pagination transparently and returns a complete issue array.

Finding the Active Sprint

GET {baseUrl}/rest/agile/1.0/board/{boardId}/sprint?state=active

Response contains values array of active sprints. Use the first result.

If values is empty: return { noActiveSprint: true, sprintName: null }. The ticket-ingestion skill handles this as an early exit with an informational message — not an error.

Fetching Issues (Paginated)

GET {baseUrl}/rest/agile/1.0/sprint/{sprintId}/issue
  ?startAt=0
  &maxResults=50
  &fields=summary,description,issuetype,labels,components,issuelinks,priority,assignee

Pagination loop:

1. Start with startAt=0
2. Collect issues from response
3. If startAt + issues.length < total: increment startAt by 50, repeat
4. Continue until all pages collected
5. Concatenate all issues arrays

Follow the rate-limiting guidance in connector-guidelines.md (100ms delay between pages for sprints > 200 issues).

Pagination failure (mid-fetch): If any page request fails after the first page succeeds, halt with:

ERROR: Jira API pagination failed at startAt={n} (fetched {n} of {total} issues).
Retry /sprint-plan to re-fetch.

Output

{
  "noActiveSprint": false,
  "sprintId": 123,
  "sprintName": "Sprint 5",
  "sprintState": "active",
  "total": 24,
  "issues": [ ... ]
}