Work item logic
Release notes, known issues, and critical and high bugs are generated from Azure DevOps queries that return work items that meet the following criteria:
Logic
Feature / backlog itemClosed
→What’s new
BugClosed
→Fixed bug
BugStill open
→Known issue
BugCritical or high severity
→Critical/high bug report
How a work item's type, state, and severity decide where its note lands.
| Work item type | State | Severity | Publish | Under the section |
|---|---|---|---|---|
| Feature or product backlog item | Closed | N/A | Yes | What's new item |
| Bug | Closed | N/A | Yes | Fixed bug |
| Bug | <> Closed | N/A | Yes | Known issue |
| Bug | <> Closed | Critical or High | N/A | Critical bug, open |
| Bug | Closed in the past 60 days | Critical or High | Yes | Critical bug, closed |
note
See Fill out work items.
The following fields are on the RN tab of all Features, Product Backlog Items, and Bugs in Azure DevOps.
| Field | What it is | Type |
|---|---|---|
| Publish | Dropdown to indicate if the work item should be published as a note | Single-select |
| Release Note | Field to write the release note | Rich HTML text |
| Product(s) Affected | Dropdown to select which product(s) the note is about | Multi-select |
| Version(s) Affected | Dropdown to select which version(s) the note applies to | Multi-select |
How the fields become notes
Selections determine which work items translate to notes, how notes are organized, and the text they contain.