> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/ticketing-and-messaging/ticket-management/jira/connecting-jira.md).

# Connecting Jira

OX supports both **Jira Cloud** and **Jira On-Prem** (Data Center / Server). For Jira Cloud, you can authenticate to Jira in one of three ways. Choose based on how you want to manage the credential and how strictly you need to scope access.

| Connection method                                                                                                                                                 | Credential is owned by | Atlassian recommendation                                                       |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------- | ------------------------------------------------------------------------------ |
| [Jira Cloud: Service account with OAuth 2.0](/ticketing-and-messaging/ticket-management/jira/connecting-jira/connecting-jira-with-a-service-account-oauth-2.0.md) | The organization       | **Recommended.** Atlassian-preferred authentication type for service accounts. |
| [Jira Cloud: Service account with API token](/ticketing-and-messaging/ticket-management/jira/connecting-jira/connecting-jira-with-a-service-account.md)           | The organization       | Supported. Use when OAuth is not an option for your organization.              |
| [Jira Cloud: Username + personal API token](/ticketing-and-messaging/ticket-management/jira/connecting-jira/jira.md)                                              | An individual user     | Legacy. Kept for existing OX deployments already using personal tokens.        |
| [Jira On-Prem (Data Center / Server)](/ticketing-and-messaging/ticket-management/jira/connecting-jira/connecting-to-jira-on-prem.md)                              | An individual user     | Self-hosted Jira; not applicable.                                              |

{% hint style="info" %}
Use a service account where possible. A service account belongs to your Atlassian organization rather than to a specific person, so the integration keeps working when employees change roles or leave. Among the service account options, [OAuth 2.0](https://claude.ai/cowork/jira-service-account-oauth.md) is preferred because it exchanges short-lived access tokens at runtime instead of presenting a long-lived API token on every request.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ox.security/ticketing-and-messaging/ticket-management/jira/connecting-jira.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.