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

# Jira

> Create an Atlassian OAuth 2.0 (3LO) integration so Voltai can read Jira issues.

**You'll create:** an Atlassian OAuth 2.0 (3LO) integration.

**We'll be able to read:** issues and user records that the connecting user can already see in Jira.

<Note>
  If you also plan to use the [Confluence connector](/connectors/confluence), you can reuse this same Atlassian integration and just add the Confluence scopes to it. We treat the two connectors independently on our side.
</Note>

## Steps

<Steps>
  <Step title="Create the integration">
    Go to [developer.atlassian.com/console/myapps](https://developer.atlassian.com/console/myapps/) and click **Create → OAuth 2.0 integration**.

    Give it a name (for example, "Voltai Jira") and accept the terms.
  </Step>

  <Step title="Add Jira API scopes">
    In the left sidebar, open **Permissions** and click **Add** on **Jira API**.

    Click **Configure** next to Jira API and grant:

    * `read:jira-work`
    * `read:jira-user`

    Atlassian adds `offline_access` automatically for refresh tokens, so you do not need to add it yourself.
  </Step>

  <Step title="Set the callback URL">
    In the left sidebar, open **Authorization**.

    Next to **OAuth 2.0 (3LO)** click **Configure**, set **Callback URL** to the [redirect URI](/connectors/introduction#redirect-uri-used-by-every-connector), and save.
  </Step>

  <Step title="Copy the credentials">
    In the left sidebar, open **Settings** and scroll to **Authentication details**.
  </Step>
</Steps>

## Send us

| Value           | Where to find it                  |
| --------------- | --------------------------------- |
| `client_id`     | Settings → Authentication details |
| `client_secret` | Settings → Authentication details |

## Things to know

* If a user has access to multiple Atlassian sites, they will see a **site picker** during the consent flow. The site they choose is the one we query for them.
* Queries use **Jira project keys** (for example `AV`), not project display names.
* Adding scopes later requires each user to disconnect and reconnect before the new scopes take effect.