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

# Extensions

> Enrich code reviews with context from issue trackers

Extensions connect your issue trackers to CloudThinker's code review agent. When the agent detects issue references in your MR/PR description or branch name, it automatically fetches the linked ticket details and uses them as context during the review — validating that the code change fulfills the requirements.

***

## Available Extensions

### Jira / Confluence

Brings Jira ticket details and Confluence specs directly into code reviews so the agent understands the business requirement behind every change.

**How it works:** When the review agent detects a Jira or Confluence link in your MR/PR description, it automatically fetches the ticket details — summary, acceptance criteria, and linked pages — and uses that context to validate whether the code change fulfills the requirement.

**Triggers:**

| Pattern                                  | Example                                                 |
| ---------------------------------------- | ------------------------------------------------------- |
| Jira URL in description                  | `https://myorg.atlassian.net/browse/OPS-1234`           |
| Confluence page URL in description       | `https://myorg.atlassian.net/wiki/spaces/.../pages/...` |
| Ticket key in description or branch name | `OPS-1234`                                              |

**Requires:** [Atlassian connection](/guide/connections/atlassian)

***

### GitHub Issues

Pulls GitHub issue context into code reviews so the agent can verify that pull requests address the linked issue requirements.

**How it works:** When the review agent finds issue references in your PR description or branch name, it fetches the issue details — title, body, labels, and comments — and reviews the code changes against those requirements.

**Triggers:**

| Pattern                          | Example                                      |
| -------------------------------- | -------------------------------------------- |
| Issue keywords in PR description | `Closes #123`, `Fixes #456`, `Resolves #789` |
| Issue reference in description   | `#123`                                       |

<Note>Only shown when your code review is configured with GitHub as the provider.</Note>

***

### GitLab Issues

Pulls GitLab issue context into code reviews so the agent can verify that merge requests address the linked issue requirements.

**How it works:** When the review agent finds issue references in your MR description or branch name, it fetches the issue details — title, description, labels, and comments — and reviews the code changes against those requirements.

**Triggers:**

| Pattern                          | Example                                      |
| -------------------------------- | -------------------------------------------- |
| Issue keywords in MR description | `Closes #123`, `Fixes #456`, `Resolves #789` |
| Issue reference in description   | `#123`                                       |

<Note>Only shown when your code review is configured with GitLab as the provider.</Note>

***

## Setup

<Steps>
  <Step title="Connect your issue tracker">
    Navigate to **Workspace Settings** > **Connections** and connect the relevant service ([Atlassian](/guide/connections/atlassian), GitHub, or GitLab)
  </Step>

  <Step title="Check the Extensions page">
    Go to **Code Review** > **Extensions** to verify the connection status shows "Connected"
  </Step>

  <Step title="Include references in your MR/PR">
    Add issue links or ticket keys to your MR/PR description. The review agent detects them automatically — no additional configuration needed.
  </Step>
</Steps>

***

## How the Agent Uses Issue Context

When the code review agent detects an issue reference, it:

1. **Fetches** the ticket or issue details (title, description, acceptance criteria, labels, comments)
2. **Validates** whether the code changes fulfill the stated requirements
3. **Flags** missing or incomplete implementations based on acceptance criteria
4. **References** the ticket context in review findings so you can see the connection between requirements and code

This is fully automatic — no commands or configuration beyond the initial connection setup.

***

## Tips

* **Include links in your MR/PR description** — the agent scans the description and branch name for references. The more context you provide, the better the review.
* **Acceptance criteria matter** — well-structured Jira tickets with clear acceptance criteria give the agent the strongest signal for validating code changes.
* **Multiple references are supported** — link as many tickets or issues as relevant. The agent fetches all of them.

***

## Related

<CardGroup cols={2}>
  <Card title="Code Review Setup" icon="gear" href="/guide/code-review/setup">
    Configure code review for your repositories
  </Card>

  <Card title="Convention Rules" icon="book" href="/guide/code-review/convention-rules">
    Customize what CloudThinker checks in your code
  </Card>
</CardGroup>