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.
ProviderTitleDescriptionCustom FieldsSubtasks / ChildrenAcceptance CriteriaAttachmentsLabels / Tags
Jira✔✔✔ (customfield_*)✔✔*✔ (≤3 images)✔
Linear✔✔✖✔✖✔ (≤3 images + embedded)✔
Azure DevOps✔ (System.Title)✔ (System.Description)✖✖✔ (dedicated field)✖✔ (System.Tags)
Monday.com✔✔✔ (long_text cols)✔✖✖✔
GitHub Issues✔✔✖✔✖✖✔
GitLab Issues✔✔✖✔✖✖✔
* 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
ProviderSupported examplesNot supported
JiraPROJ-123
proj-123
feature/PROJ-123
feature/PROJ-123/add-new-feature
feature/PROJ-123-add-new-feature
fix-PROJ-123-bug
TSAASO-3250-cluster-labels
ABC-5678_v2
[PROJ-123]-hotfix
release-v1.2-PROJ-123-impl		bugfix-abc-456-fix
PROJ123
P-123
PROJ1-123
VERYLONGPROJECT-123
PROJ-12345678
LinearPLT-2837
plt-2837
plt-2837-be-rename-env-file
A1B2-456
feature/PLT-2837
feature/PLT-2837-add-feature
release/v1.2/PLT-2837
hotfix/ABC-123/urgent		fix-PLT-2837
bugfix_PLT-2837
feature-PLT-2837-bug
[PLT-2837]
PREFIX/feature-PLT-2837
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: 
[pr_reviewer]
require_ticket_analysis_review = false
You can also enable detection of unrelated changes: 
[pr_reviewer]
check_pr_additional_content = true
When enabled, Qodo flags changes that appear unrelated to the stated intent and notes them in the review. This setting is disabled by default.

​
Configuration options

By default, the tool will automatically validate if the PR complies with the referenced ticket. If you want to disable this feedback, add the following line to your configuration file: 
[pr_reviewer]
require_ticket_analysis_review=false
You can also enable detection of unrelated changes: 
[pr_reviewer]
check_pr_additional_content=true
When enabled, Qodo flags changes that appear unrelated to the stated intent and notes them in the review. This setting is disabled by default.