Skip to main content

Sprint Completion → Release Content

Scenario

When a sprint closes, marketing needs release notes and a changelog, not a list of Jira keys. This job pulls the most recently completed sprint, fetches all resolved issues, categorizes by type, then chains two Mavera Generate calls for polished release notes and a changelog. Flow: Jira GET /board/{id}/sprint (completed) → GET /sprint/{id}/issue (done) → categorize → Mavera POST /api/v1/generations (release notes + changelog)

Code

Example Output

Error Handling

The Agile API returns 404 if the board ID is wrong or the token lacks access. Verify via GET /rest/agile/1.0/board.
Sprints can close with unresolved issues (moved to backlog). The code filters on resolution != null. If all issues were moved, skip generation.
Sprint and board endpoints use /rest/agile/1.0, not /rest/api/3. Mixing them causes 404s.