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

# Jira Integration

> Connect Jira so Greptile reviews pull requests against related tickets

When you connect Jira, Greptile finds Jira tickets related to your pull requests and reviews the code against the requirements.

<Note>
  **Prerequisites:** Authorizing the connection to Jira requires admin access. Once authorized, the context applies to every repository in the organization.
</Note>

## What Greptile Does with Your Tickets

* **Greptile finds the ticket.** It reads issue keys and links from the pull request title, description, and branch name, and it can search Jira for related work.
* **Greptile reviews the code against the ticket.** The description and acceptance criteria become review context, so Greptile can point out where a change does not do what the ticket asked for.
* **Greptile answers follow-up questions.** Ask about a Jira ticket in a reply to a Greptile comment, and Greptile looks it up.
* **Greptile shows what it read.** Every ticket it opened is linked in the review.

## Connect Jira

<Steps>
  <Step title="Open Integrations">
    Go to [Memory → Integrations](https://app.greptile.com/-/custom-context/integrations) in the Greptile dashboard.
  </Step>

  <Step title="Add Atlassian">
    Click **Add new data source** and select **Atlassian**.
  </Step>

  <Step title="Authorize Greptile">
    Atlassian asks you to grant Greptile read access. Choose the site you want to use it on, then click **Accept**.

    <Frame>
      <img src="https://mintcdn.com/greptile/pPDrEYn7_-Bi_2Mg/images/greptile-connect-jira.png?fit=max&auto=format&n=pPDrEYn7_-Bi_2Mg&q=85&s=9295926011af91408a982335e8b8f8b1" alt="Atlassian consent screen granting Greptile read access to Jira and Confluence" width="677" height="851" data-path="images/greptile-connect-jira.png" />
    </Frame>
  </Step>

  <Step title="Confirm the connection">
    Atlassian now appears in your list of connected data sources. Greptile uses Jira context on the next review.
  </Step>
</Steps>

<Note>
  Greptile reads Jira today. The connection already covers Confluence, so you will not need to reconnect when Greptile starts reading Confluence pages.
</Note>

## Where Tickets Appear in Reviews

A comment that depends on a ticket ends with a **Source Used** line linking to it, and the review summary lists everything Greptile read under **Context used**. Jira tickets are labeled **Atlassian** there, after the connection they come from.

Greptile cites only the tickets it actually opened, and it says when a ticket came from its own search rather than from your pull request.

## What Greptile Can Read

The connection is read-only, so Greptile never writes to Jira. Greptile reads Jira as the Atlassian account that authorized the connection, which means it sees any ticket that account can see.

Greptile reads one Atlassian site: the site you chose when you authorized the connection. Email [support@greptile.com](mailto:support@greptile.com) if you need to point it at a different one.

## Manage the Connection

Any member of your organization can see the connected data sources under [Memory → Integrations](https://app.greptile.com/-/custom-context/integrations), and admins can add or remove them there.

To turn the integration off, click the disconnect icon on the **Atlassian** row and confirm. Greptile deletes the stored credentials, and reviews continue without ticket context.

## Next Steps

<CardGroup cols={2}>
  <Card title="Linear Integration" icon="list-check" href="/docs/linear-integration">
    Connect Linear to give reviews the same kind of issue context.
  </Card>

  <Card title="Common Issues" icon="wrench" href="/docs/troubleshooting/common-issues">
    Troubleshoot reviews that are not picking up ticket context.
  </Card>
</CardGroup>