Issue tracker integrationbeta

Angada can check whether a pull request meets the requirements in its linked Linear, Jira, Asana, or GitHub issue. Connect your issue tracker so reviews verify a change against the objectives in the linked issue. Angada also uses the issue for context when it reviews the code and writes the PR description.

You need the Admin role to connect or disconnect an issue tracker. See Roles and permissions for details.

How it works

When you open a pull request with a linked issue, Angada:

1. Finds the issue — Looks for an issue ID like ABC-123 in the PR title or branch name. For GitHub Issues, it uses the issue the PR closes, such as Fixes #123.
2. Reads the requirements — Extracts the requirements from the issue description.
3. Checks the code — Compares the changed files against those requirements.
4. Shows the results — Posts a table on the PR review listing which requirements the change meets and which are still missing.

Issue analysis runs as part of the normal AI Review. You do not need to start a separate review.

Requirements

For issue analysis to run:

• Link an issue — Include the issue ID in the PR title or branch name. For GitHub Issues, link the issue on GitHub.
• Add requirements — The issue must have a description with clear objectives.
• Enable AI Review and connect your tracker — AI Review must be enabled, and the issue tracker must be connected in Settings → Integrations.

Writing good requirements

Angada reads requirements written as:

• Bullet points or numbered lists
• Sections labeled Acceptance Criteria or Requirements
• Action items starting with Should, Must, or Can

Good example

## Acceptance Criteria
- User can submit the contact form
- Form shows validation errors for an invalid email
- Form data is saved to the database
- User receives a confirmation message

What doesn't work

Make the form work better.

This is too vague to analyze. Angada can't tell whether the change meets it, so the result is unreliable.

What you'll see in reviews

Angada posts a requirements table on the pull request review. Each row pairs a requirement from the linked issue with whether the change meets it:

This is an illustration, not an example review. The rows come from your linked issue, and the status reflects only the files changed in the pull request.

Troubleshooting

For how linked context appears alongside code findings, see Anatomy of a Review.