Skip to main content
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.
This connector is for self-hosted Jira Data Center. For Atlassian-hosted Jira, use the Jira connector. The two are configured independently and can be enabled side by side.

​
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

1

Open application links

In Jira, go to Administration → Applications → Application links and click Create link.
2

Choose an incoming external application

Select External application, then Incoming, and continue.
3

Name it and set the redirect URL

Give it a name (for example, “Voltai”) and set Redirect URL to the redirect URI.
4

Grant read permission

Under Permission, choose Read. Voltai never requests write access.
5

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.

​
Send us

​
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

We have not yet stored your base_url and credentials. Send them to your Voltai contact using the table above.
The instance is older than 9.12. Upgrade Jira Data Center, then connect again.
Jira no longer accepts the stored token. Click Reconnect. If it fails again, ask your Jira admin to confirm the application link still exists.
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.