> ## 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 Data Center

> Create an incoming OAuth 2.0 application link in your self-hosted Jira Data Center so Voltai can read issues.

**You'll create:** an incoming OAuth 2.0 application link in Jira Data Center.

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

<Note>
  This connector is for self-hosted **Jira Data Center**. For Atlassian-hosted Jira, use the [Jira connector](/connectors/jira). The two are configured independently and can be enabled side by side.
</Note>

## Requirements

* Jira Data Center **9.12 or later**. Voltai checks the version when a user connects and refuses older instances.
* The instance is served over **HTTPS** and reachable from Voltai at its base URL — for example `https://jira.example.com`, or `https://intranet.example.com/jira` when Jira runs under a context path.
* A Jira administrator to create the application link.

## Steps

<Steps>
  <Step title="Open application links">
    In Jira, go to **Administration → Applications → Application links** and click **Create link**.
  </Step>

  <Step title="Choose an incoming external application">
    Select **External application**, then **Incoming**, and continue.
  </Step>

  <Step title="Name it and set the redirect URL">
    Give it a name (for example, "Voltai") and set **Redirect URL** to the [redirect URI](/connectors/introduction#redirect-uri-used-by-every-connector).
  </Step>

  <Step title="Grant read permission">
    Under **Permission**, choose **Read**. Voltai never requests write access.
  </Step>

  <Step title="Copy the credentials">
    Save. Jira shows a **Client ID** and **Client secret**. They remain visible in the application link's details if you need them again later.
  </Step>
</Steps>

## Send us

| Value           | Where to find it                                               |
| --------------- | -------------------------------------------------------------- |
| `base_url`      | Your Jira base URL, including any context path such as `/jira` |
| `client_id`     | Application link → credentials                                 |
| `client_secret` | Application link → credentials                                 |

## Things to know

* Each user connects individually from **Settings → Integrations** and approves read access on Jira's own consent screen. Results are limited to what that user can already see in Jira.
* Voltai requests the `READ` scope only and renews tokens automatically. It reads issue summaries, status, and descriptions as Jira renders them, shows image attachments to the assistant, and reads text-based attachments up to 1 MB.
* If the application link is deleted or a user's Jira account is deactivated, that user's Integrations card shows **Connection expired** with a **Reconnect** button.
* Queries use **Jira project keys** (for example `AV`), not project display names.

## Troubleshooting

<AccordionGroup>
  <Accordion title="&#x22;Jira Data Center is not configured for this organization&#x22; when clicking Connect">
    We have not yet stored your `base_url` and credentials. Send them to your Voltai contact using the table above.
  </Accordion>

  <Accordion title="&#x22;Jira Data Center 8.x is not supported&#x22;">
    The instance is older than 9.12. Upgrade Jira Data Center, then connect again.
  </Accordion>

  <Accordion title="Jira reports a redirect URI error on the consent screen">
    The **Redirect URL** in the application link does not match our redirect URI exactly. Ask your Jira admin to correct it — including the trailing slash.
  </Accordion>

  <Accordion title="Connection expired, or replies say Jira rejected the credentials">
    Jira no longer accepts the stored token. Click **Reconnect**. If it fails again, ask your Jira admin to confirm the application link still exists.
  </Accordion>

  <Accordion title="Issues you can see in Jira are missing, or replies mention a 404">
    A 404 usually means the `base_url` we hold is missing the context path (for example `/jira`). Confirm the value with your Voltai contact. Missing results otherwise reflect your own Jira permissions.
  </Accordion>
</AccordionGroup>