Question

Your team runs sprints in Azure Boards and deploys via Azure Pipelines. Product management wants an automatically generated release notes document published to the team wiki after each successful production deployment. The notes must list all completed User Stories and Bugs associated with the commits included in that release, without requiring anyone to manually curate the list. Which approach best satisfies this requirement with the least ongoing maintenance?

Accepted Answer

Add a pipeline step that uses the built-in release notes generation to collect associated work items from the build's linked commits and publish the output as a Markdown page to the wiki via the Azure DevOps REST API.

Answer

Create a shared query in Azure Boards filtered by iteration path and manually copy its results into the wiki after each deployment.

Answer

Configure a Teams channel webhook so that every work item state change posts a message, then archive the channel history as the release notes.

Answer

Enable a dashboard widget showing the sprint burndown and export it as a PDF attached to each release.