Work items & ticket sources
How codingassist.bot resolves the ticket behind a PR — Azure DevOps Boards, Jira, Linear and GitHub Issues — so acceptance criteria can be verified.
Acceptance-Criteria verification only works if we can find the ticket behind a pull request. codingassist.bot resolves work items during the Context stage, from whichever provider your team uses — then feeds the acceptance criteria into the review.
Supported sources
| Source | How a PR links to it | Status |
|---|---|---|
| Azure DevOps Boards | Native PR ↔ work-item links | |
| Jira | ID in the branch / PR title (PROJ-123) | |
| Linear | ID in the branch / PR title (ENG-456) | |
| GitHub Issues | #789 / "Fixes #789" in the PR |
Azure DevOps — two-step resolution
Azure DevOps PR events don't carry work items, so codingassist.bot resolves them with two REST calls during Stage 1:
Other providers — ID discovery
For Jira, Linear and GitHub Issues, the identifier is discovered from the PR itself, then the item is fetched from the provider:
Explicit links first
Native PR ↔ work-item links (Azure DevOps) always win when present.
Branch name
A convention like
feature/PROJ-123-rate-limitingyieldsPROJ-123.PR title / description
Falls back to an ID or
Fixes #789in the PR body.
Smart defaults
The ticket source defaults to your source control: an Azure DevOps repo → ADO Boards; a GitHub repo → GitHub Issues. An Admin can override the provider under Settings → Integrations.