Work items
How codingassist finds the Azure DevOps work items behind a pull request, what it reads from them, and the limits that apply.
codingassist finds the work items behind a pull request during Stage 1 and passes their acceptance criteria to the AI review. Without a work item, the code review still runs, but the acceptance criteria check is skipped.
Supported sources
| Source | Status |
|---|---|
| Azure DevOps Boards | Supported |
| Jira | Not supported yet |
| Linear | Not supported yet |
| GitHub Issues | Not supported yet |
Turn work item reading on
codingassist reads work items only when the work item provider is Azure DevOps Boards. To make sure it is set for a repository, add this to the repository's .praxiom.yml:
version: 1
workItem:
provider: AzureDevOpsBoardsIf the summary comment shows the AC match score as n/a on a pull request that has a linked work item, this setting is the first thing to check.
How work items are found
codingassist collects work item ids from two places:
- Links on the pull request: the work items linked to it in Azure DevOps.
- A reference in the text: the first
AB#123found in the branch name, then the title, then the description.
Duplicates are removed and at most 10 work items are read per review.
For each work item, codingassist also reads its parent, one level up: the user story above a task, for example. Features and epics above that are not read.
What is read
| Field | Used for |
|---|---|
| Title, description, type | Context for the AI review |
| Acceptance Criteria | The criteria to verify. See Acceptance criteria verification |
| Parent work item | Context, and up to five of its criteria |
codingassist calls the Azure DevOps REST API with the organization's connection: pullRequests/{id}/workitems for the links, then wit/workitems/{id} for each item.
Limits
- Work item content is cached for 24 hours. A change to a work item can take up to 24 hours to appear in reviews.
- Each criterion is truncated to 300 characters in the review prompt.