Skip to main content
GitHubJiraLinearAzure DevOps
Qodo enhances the code review process by integrating with your ticket management system. It automatically surfaces relevant ticket data alongside code changes, helping reviewers understand the intent behind a pull request. Qodo supports both native ticketing integrations (where the repository and ticketing system are hosted on the same platform) and external ticketing integrations, which can be used alongside supported repository platforms.

​
Ticket data fetched

The table below shows which ticket fields are fetched and used by Qodo for ticket context and compliance, per provider. * Acceptance criteria in Jira is supported only when stored in a custom field.

​
Ticket recognition criteria

A ticket is linked to a PR if:
  • The PR description contains a direct link to the ticket, or
  • The branch name matches an accepted ticket reference pattern (see accepted syntax for details)
Accepted syntax
Notes:
  • Branch-based detection is always enabled
  • Supported patterns are fixed in production and cannot be configured
  • Matching is case-insensitive
  • The ticket ID must appear at the start of the branch name or immediately after a /

​
Code review behavior

​
Context-aware analysis

When a pull request references a ticket or requirement, Qodo uses the available context (such as title and description) to better understand the intent behind the changes. This context informs both the generated pull request description and the review feedback.

​
Requirement alignment feedback

During review, Qodo evaluates how well the changes align with the stated intent and surfaces feedback as findings rather than explicit compliance statuses. This may include:
  • Missing or incomplete requirements
  • Changes that do not clearly support the intended goal
  • Notes indicating that the implementation looks correct but may require additional manual validation (for example, UI testing)

​
Configuration options

By default, requirement-aware feedback is included in reviews. To disable it:
You can also enable detection of unrelated changes:
When enabled, Qodo flags changes that appear unrelated to the stated intent and notes them in the review. This setting is disabled by default.

​
Get started

See the setup guide for each supported tool:

Jira

Surface issue requirements, acceptance criteria, and subtasks during review. Supports Jira Cloud and Jira Data Center.

Linear

Link Linear issues to pull requests for context-aware review.

GitHub Issues

Link GitHub Issues to pull requests for context-aware review.

Azure DevOps

Surface Azure Boards work item context and acceptance criteria during review.