> 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/jira.md).

# Connecting Jira with User Name & Token

This page describes how to connect OX to **Jira Cloud** using a personal Atlassian account's email address and API token.

{% hint style="info" %}
The recommended path for new Jira Cloud integrations is [Connecting Jira with a Service Account](/ticketing-and-messaging/ticket-management/jira/connecting-jira/connecting-jira-with-a-service-account.md). This page is preserved for existing deployments that already use the personal-token method.
{% endhint %}

## Prerequisites

A Jira account.

## Step 1: Getting Jira token \[Jira]

1. Log in to your Atlassian account.
2. From your profile picture in the top-right corner, select **Profile**.

<figure><img src="/files/7G66hFWXjiyK5XHsL4rw" alt="" width="563"><figcaption></figcaption></figure>

3. In your profile settings page, select **Manage your account** and then select **Security**.

<figure><img src="/files/jUNtqqGVUtbZYn9Ou6bz" alt="" width="563"><figcaption></figcaption></figure>

4. Scroll down to the **API Tokens** section, select **Create and manage API tokens**, and then select **Create API token.**
5. In the **Create API token** dialog, define the following.

<figure><img src="/files/Tm5COjB0Zk04GJ7TtEKh" alt="" width="563"><figcaption></figcaption></figure>

<table><thead><tr><th width="274">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>A significant name that makes it easy to identify the purpose of the token.</td></tr><tr><td><strong>Expires on</strong></td><td>Set the expiration date as far as possible.</td></tr></tbody></table>

6. Select **Create**. The dialog with the token appears.

<figure><img src="/files/aHahn8EF5qQwp7uXhS3f" alt="" width="563"><figcaption></figcaption></figure>

7. Copy the token and store it in a safe location.\
   After closing this dialog you cannot see it again.

## Step 2: Connecting to Jira \[OX]

1. In the **OX app**, go to **Connectors** and search for Jira.

<figure><img src="/files/BfzptSf2r8DQFolSkcjn" alt="" width="293"><figcaption></figcaption></figure>

2. Select **Jira** and set the following parameters in the **Configure your Jira credentials** dialog.

<figure><img src="/files/bmK5mHFtH6aE0JX8TFb7" alt="" width="499"><figcaption></figcaption></figure>

| Parameter         | Description                                         |
| ----------------- | --------------------------------------------------- |
| **Jira Host URL** | Add your organization account URL.                  |
| **User Name**     | Type the email address used as your Jira user name. |
| **Token Name**    | Paste the Jira token you have created.              |

3. Leave [**OX Broker** ](/get-started/onboarding-to-ox/prerequisites-and-access/ox-broker.md)off and **Bypass SSL Verification** not selected unless your environment specifically requires them.
4. Select **CONNECT**. The success message appears.

## [Step 3: Adding Jira Tickets](/ticketing-and-messaging/ticket-management/jira/adding-jira-tickets.md)


---

# 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/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.