Lab: GitHub Flow, Issues, Projects, and Azure Boards

Outcome

Run a small issue-to-merge feedback loop in GitHub, connect the repository to Azure Boards, and prove the work item, branch, commit, pull request, check, release, and feedback closure are traceable in both views.

Do

1. Create a GitHub Issue with acceptance criteria, owner, label, and GitHub Project field/status. Enable a scoped notification for assignment or mention; record the owner and route. Create the matching Azure Boards work item.
2. Connect the Azure Boards project to the GitHub repository through Project settings > GitHub connections using the approved app/account. In a feature branch, reference AB#<id> in commit/PR text, open a PR, satisfy its protection, merge it, and verify Development links in Azure Boards and linked work/PR in GitHub.
3. Add release/deployment evidence and a short feedback comment to the work item/issue. Move the project/work item to the completed state only after the feedback is reviewed; record the trace chain.

Verify

Capture issue/project fields, notification, Azure Boards connection, linked branch/commit/PR/check, release evidence, and feedback-closeout state. You should now understand: GitHub Flow supplies a small branch-to-main loop; Projects and Boards track work; integration links artifacts but does not replace an owner’s decision.

Break and fix

1. Omit AB# or link the wrong work item; diagnose the connection, repository scope, link syntax, and Development view, then correct it.
2. Remove the issue owner or mute the needed notification. Identify the missed handoff, restore a scoped notification/owner, and verify delivery.
3. Try to close work before the check or feedback is complete. Restore the open state and complete the evidence chain.

Scenario practice

1. Configure: Define issue fields, project status, Board work-item state, notification owner, and GitHub Flow protection for a defect.
2. Diagnose: A merged PR is absent from Azure Boards. Inspect connection, repo authorization, work-item reference/link, merge state, and synchronization delay.
3. Distinguish: Contrast GitHub Issue/Project, Azure Boards work item, branch, PR, commit, release, and customer feedback.

Clean up

Remove the training connection only if no other test repo needs it; delete test issue/project/work item/branch/PR and notifications after recording evidence.

Sources and re-audit

• Connect Azure Boards to GitHub, checked 2026-08-22.
• Azure Boards app for GitHub, checked 2026-08-22.

Re-audit when cross-platform artifact linking or notification behavior changes.

Related

github-flow · github-issues-projects · azure-boards · devops-traceability · All labs