Azure Boards and GitHub linking: '#N' vs 'AB#N'
Verdict: '#N' targets a GitHub issue; 'AB#N' an Azure Boards work item. A bare reference links only; a fix keyword on merge to the default branch closes the issue or transitions the work item to Resolved, else Completed.
| Criterion | #123 (GitHub issue) | AB#234 (Boards work item) |
|---|---|---|
| Refers to | A GitHub issue in the repository | An Azure Boards work item |
| Bare reference | Links the issue | Links the work item, no state change |
| Fix keyword on merge to default branch | Closes the GitHub issue | Transitions to first Resolved-category state, else first Completed |
| Querying linked items | n/a | No GitHub-link field; query External Link Count > 0 |
Rules
- 'Fixed AB#' transitions the work item to the first Resolved-category state; with no Resolved state defined it falls back to the first Completed-category state.
- Work items cannot be queried by their GitHub links; query for External Link Count > 0 to surface items carrying external links.
- '#123' is a GitHub issue reference and 'AB#234' an Azure Boards work item reference; one message can link both at once.
Traps
- Azure Boards does not invent a state named 'Fixed'; the keyword maps to the Resolved category, falling back to Completed.
- There is no queryable 'GitHub Link' field; 'Integrated in build' is YAML build traceability, not a general GitHub-link filter.
- A bare '#123' is not ignored - it links on the GitHub side as an issue reference.