> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qodo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Ticketing integrations

<Warning>
  **Git Integration (formerly Qodo Merge)** – AI code review agents for pull requests. This documentation describes the Qodo v1 experience. For the Qodo v2 documentation, click [here.](/code-review)
</Warning>

<Note>
  **Platforms supported:** GitHub, Jira, Linear, Azure DevOps
</Note>

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.

### Ticket data fetched

The table below shows which ticket fields are fetched and used by Qodo for ticket context and compliance, per provider.

| Provider          | Title              | Description              | Custom Fields        | Subtasks / Children | Acceptance Criteria | Attachments              | Labels / 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

| Provider   | Supported examples                                                                                                                                                                                                                                                                                             | Not supported                                                                                                          |
| ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| **Jira**   | `PROJ-123` <br />`proj-123` <br />`feature/PROJ-123`<br /> `feature/PROJ-123/add-new-feature` <br />`feature/PROJ-123-add-new-feature` <br />`fix-PROJ-123-bug` <br />`TSAASO-3250-cluster-labels`<br /> `ABC-5678_v2`<br /> `[PROJ-123]-hotfix`<br /> `release-v1.2-PROJ-123-impl` <br />`bugfix-abc-456-fix` | `PROJ123`<br /> `P-123` <br />`PROJ1-123` <br />`VERYLONGPROJECT-123` <br />`PROJ-12345678`                            |
| **Linear** | `PLT-2837`<br /> `plt-2837` <br />`plt-2837-be-rename-env-file`<br /> `A1B2-456`<br /> `feature/PLT-2837`<br /> `feature/PLT-2837-add-feature`<br /> `release/v1.2/PLT-2837`<br /> `hotfix/ABC-123/urgent`                                                                                                     | `fix-PLT-2837`<br /> `bugfix_PLT-2837`<br /> `feature-PLT-2837-bug`<br /> `[PLT-2837]`<br /> `PREFIX/feature-PLT-2837` |

<Note>
  **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 `/`
</Note>

### Tool behavior

#### Describe tool

When a ticket is recognized, the describe tool includes ticket content (title, description, labels) in its analysis. This provides the model with additional context for understanding the purpose behind the code changes.

#### Review tool

The review tool also incorporates ticket context into its analysis. Additionally, it evaluates whether the PR aligns with the ticket’s intent, assigning one of the following labels:

* **Fully Compliant:** PR directly addresses the ticket requirements

* **Partially Compliant:** PR covers some but not all of the requirements

* **Not Compliant:** PR does not align with the ticket’s intent

* **PR Code Verified:** Code appears valid for the ticket, but additional manual testing (e.g., UI checks across devices) is required

<Frame>
  <img src="https://mintcdn.com/qodo/0Lwij7lmM5KGq-6-/images/v1/pr_agent_Fticket_compliance_review.png?fit=max&auto=format&n=0Lwij7lmM5KGq-6-&q=85&s=fb3676a891642e6188719aba6b04c81f" alt="" width="910" height="308" data-path="images/v1/pr_agent_Fticket_compliance_review.png" />
</Frame>

## 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](/v1/configuration/configuration-file):

```bash theme={null}
[pr_reviewer]
require_ticket_analysis_review=false
```

You can also set:

```bash theme={null}
[pr_reviewer]
check_pr_additional_content=true
```

When enabled, Qodo will check that all code changes are related to the ticket. If unrelated content is found, the PR will be downgraded (e.g., to **PR Code Verified**), and a comment will indicate the extra content. The default is `false`.