Question

Your team uses GitHub for source control and Azure Boards for planning. Developers follow GitHub Flow, creating short-lived feature branches merged via pull requests. The product owner complains that when a work item is marked 'Done' in Azure Boards, there is no visibility into whether the code implementing that work item has actually reached production. You need to design a feedback cycle that surfaces the real deployment state of each work item back to the board with minimal custom development. Which approach best achieves this?

Accepted Answer

Configure the Azure Boards-GitHub integration to link commits and PRs, and use Azure Pipelines deployment jobs targeting environments so that Deployment records automatically appear on the linked work items' Development section.

Answer

Add a custom 'Deployed' state to the work item workflow and require developers to manually update it after each production release.

Answer

Create a dashboard cycle time widget filtered to the Done state so stakeholders can infer deployment timing from the average duration.

Answer

Enable branch policies requiring linked work items on every pull request so the board reflects merge status as the deployment indicator.