Do you link commits, branches, and PRs to a PBI?

To improve visibility into what work has been done, link your PBIs and tasks to the related commits, branches, and pull requests. Every commit, branch, and PR should be associated with a PBI.

❌ Figure: Bad example - No linked commits, branches or pull requests

✅ Figure: Good example - Git branch linked to PBI in Azure DevOps

Using Azure DevOps

If you create branches through Azure DevOps, you can link them to a work item during the creation process.

✅ Figure: Good example - Using Azure DevOps to link PBI during creation

Learn more on this article: Linking Work Items to Git Branches, Commits, and Pull Requests.

Automating rule enforcement

You can setup Branch Policies on your main branches to enforce this behaviour.

✅ Figure: Good example - Branch Policy on the master branch to enforce linked work items on pull requests