Use cases
Documents from Azure DevOps work items
Turn the work items your team maintains into release notes, test reports and documents for review. Choose the document your readers need below. Each guide includes a starter template, setup instructions, an illustrative example and plan requirements.
30 days, every feature, no credit card. The trial does not convert into a paid plan automatically.
For teams preparing their next release
Release notes
One template, every release
Generate release notes from Azure DevOps work items. Review features and fixes in a saved template, then export PDF, HTML or Markdown. Works in the UI and pipelines.
Release notes with Bravo Notes →For QA leads and teams that hand test evidence to customers or auditors
Test reports
Steps, outcomes and coverage in one document
Generate test reports from Azure DevOps: test cases with steps and expected results, pass and fail counts per suite, and requirement coverage, exported as PDF, HTML or Markdown.
Test reports with Bravo Notes →For product owners, team leads and project managers
Sprint reports
A report stakeholders can read without opening Azure DevOps
Create sprint reports from Azure DevOps work items. Separate completed and open work in a saved template, then export a PDF or schedule a Wiki update.
Sprint reports with Bravo Notes →For business analysts, product owners and delivery teams
Requirements documents
Keep requirements in Azure DevOps and send a review copy
Generate a requirements document from Azure DevOps work items: descriptions, acceptance criteria, images and linked test cases in a saved template, exported as PDF, HTML or Markdown.
Requirements documents with Bravo Notes →For product and release teams that write for customers
Customer-facing changelogs
Keep customer wording alongside the work item
Create customer-facing changelogs from Azure DevOps. Keep release wording in a custom field, review the selected changes and export HTML, Markdown or PDF.
Customer-facing changelogs with Bravo Notes →
Plans apply to one Azure DevOps organization and include named creator seats. Readers of exported files do not need a Bravo Notes license. Test Plans integration and Confluence publishing require Business or above. Compare plans.
How Bravo Notes works
Three steps inside Azure DevOps. The template and its rules are saved, so the next release is the same three steps again.
Step 1
Add work items
Pick a saved query, a build or release, a sprint, or select items on the backlog. In a pipeline, the build task loads them for you.
Step 2
Apply a template
Label rules sort work items into sections such as new features and fixed bugs. The template decides which fields appear and how.
Step 3
Export or publish
Download PDF, HTML or Markdown, or publish to an Azure DevOps Wiki, a repository, Confluence, email or a Teams channel.
Try Bravo Notes free for 30 days
Install the extension from the Visual Studio Marketplace into your Azure DevOps organization. The trial includes every feature, needs no credit card and does not convert into a paid plan automatically.