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

# Adding Jira Tickets

After establishing the [connection with Jira](https://docs.ox.security/ticketing-and-messaging/ticket-management/jira.md), you can add Jira tickets for a variety of tasks and issues, and [add automation to tickets](https://docs.ox.security/ticketing-and-messaging/ticket-management/jira/automating-jira-ticketing-in-ox.md).

You can add Jira tickets in OX using one of the following methods:

* Adding a new ticket to an issue on the Active Issues page, or bulk of issues.
* Adding a new ticket as a scheduled task using workflows.

<figure><img src="https://884876233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdK3XMLdV8zRg847RmGmZ%2Fuploads%2Fgit-blob-9eb60a075f5d9855d44556de36a9a4bbda79cf52%2FWF_Jira_ticket.png?alt=media" alt="" width="204"><figcaption></figcaption></figure>

In addition to creating and updating Jira tickets, you can use workflows to [automatically synchronize Jira ticket status with the status of the associated OX issue](#change-jira-status-to-to-do-if-the-ox-issue-is-active).

## **Add a new Jira ticket in OX**

1. On the Active Issues page, identify and select the issue(s) for which you want to add a new ticket(s) in Jira.
2. Select the Jira icon.

<figure><img src="https://884876233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdK3XMLdV8zRg847RmGmZ%2Fuploads%2Fgit-blob-4eb8c5280041c629e4d38764f78ac7b20534a7c6%2FJira_icon_issue.png?alt=media" alt=""><figcaption></figcaption></figure>

3. Set the ticket mandatory parameters in the **Create Jira Issue** dialog.

<figure><img src="https://884876233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdK3XMLdV8zRg847RmGmZ%2Fuploads%2Fgit-blob-61f6768043f323127d686b0158695f66f43a4760%2FModern%20Jira%20Issue%20Creation%20Dialog.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

| Parameter      | Description                                                                                    |
| -------------- | ---------------------------------------------------------------------------------------------- |
| **Summary**    | The title of the ticket that describes the problem/issue, as it appears in the OX Issues page. |
| **Project**    | The name of the project, as it's defined in Jira.                                              |
| **Issue Type** | Select the issue type.                                                                         |

4. (Optional)Set the other Jira ticket parameters.
5. Select **SUBMIT**.

The new ticket appears in Jira.

<figure><img src="https://884876233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdK3XMLdV8zRg847RmGmZ%2Fuploads%2Fgit-blob-1f02a7c71ef197d950390c3a1cdfa4050a41e9e6%2FJira_new_ticket.png?alt=media" alt=""><figcaption></figcaption></figure>

## Creating Jira tickets in bulk

You can create Jira tickets for multiple OX issues at once from the Active Issues page. By default, OX creates a separate Jira ticket for each selected issue.

**To create a Jira ticket for each issue:**

1. Go to **Active Issues** and select the checkboxes next to the issues.
2. Select the **Jira** action on the toolbar.
3. Select **Create a ticket per issue**, if the ticket creation options are displayed.

<figure><img src="https://884876233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdK3XMLdV8zRg847RmGmZ%2Fuploads%2Fgit-blob-9a9f98f8b57af54a23c59c1bc775572778926f2a%2Fjira_ticket_per_issue.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

4. Select the Jira connection and project, and complete the required fields.
5. Select **Submit**.

OX creates a separate Jira ticket for each selected issue. Other connected ticketing systems also support creating separate tickets in bulk.

### Creating a single Jira ticket for multiple issues

**Note:** This Jira capability is available in Early Access.

You can link multiple OX issues to one Jira ticket instead of creating a separate ticket for each issue.

**To create one Jira ticket for multiple issues:**

1. Go to **Active Issues** and select the issues to include.
2. Select the **Jira** action on the toolbar.
3. Select **Create a single ticket for multiple issues**.

<figure><img src="https://884876233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdK3XMLdV8zRg847RmGmZ%2Fuploads%2Fgit-blob-98787bdddb848794a514c490ee4781751d7c9532%2FJira_Issue_multiple.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

4. Under **Select Token**, select the Jira connection if more than one is available.
5. Enter a **Summary** for the combined ticket.
6. Select the **Project** and **Issue Type**, and complete any other required Jira fields.
7. Select **Submit**.

The Jira ticket description contains a table of the linked OX issues. Comments provide additional issue details and recommendations, with links back to OX.

When OX issues are subsequently linked or unlinked, OX adds comments to Jira rather than editing or deleting existing ticket content.

## Change Jira status to To Do if the OX issue is still active

If you move a Jira ticket to **Done** while the associated OX issue is still active in OX, you can use a workflow to automatically move the Jira ticket back to **To Do**.

1. On the **Workflows** page, select **Create New Workflow**.

<figure><img src="https://884876233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdK3XMLdV8zRg847RmGmZ%2Fuploads%2Fgit-blob-add6b1504ca51c54d6017e981fd201b6462a5704%2FWF0%20-%20New%20Workflow.png?alt=media" alt="" width="512"><figcaption></figcaption></figure>

2. Select **Create**.
3. Select a new trigger.
4. Add a **Jira Status** condition.
5. Select the Jira status **Done**.

<figure><img src="https://884876233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdK3XMLdV8zRg847RmGmZ%2Fuploads%2Fgit-blob-1b9a567c995b74f317a69903c7825296f782a803%2FWF4%20-%20New%20Workflow%20-%20Condition%20Details.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

6. Add a **Jira Transition Status** action.

<figure><img src="https://884876233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdK3XMLdV8zRg847RmGmZ%2Fuploads%2Fgit-blob-ee1fef0cfe7de93c81a107332065247d1564864f%2FWF5%20-%20New%20Workflow%20-%20Action%20Picker.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

7. Select the target Jira status **To Do**.

<figure><img src="https://884876233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdK3XMLdV8zRg847RmGmZ%2Fuploads%2Fgit-blob-bdd0fa34ddee171b1012360233fcbbdd35a9279c%2FWF6%20-%20New%20Workflow%20-%20Action%20Details.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

8. (Optionally) Select a Jira project to limit the list of available target statuses.

**Notes:**

* The transition must exist in your Jira workflow.
* The transition must be a direct transition between the selected statuses.
* The transition cannot require additional mandatory fields.
* Cross-project transitions are not supported.

9. Select **Save Changes**.

<figure><img src="https://884876233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdK3XMLdV8zRg847RmGmZ%2Fuploads%2Fgit-blob-7565f8bc32c2a18d277ed72c9abdb7f72a972891%2FWF7%20-%20New%20Workflow%20-%20Prepared.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

10. Enable the workflow.

<figure><img src="https://884876233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdK3XMLdV8zRg847RmGmZ%2Fuploads%2Fgit-blob-85c02c4dd4f2c80de21edd73c0c03145b76d2cf1%2FWF8%20-%20New%20Workflow%20-%20Enable.png?alt=media" alt="" width="504"><figcaption></figcaption></figure>

11. Run the workflow manually or wait for it to run automatically based on the configured trigger.

The workflow appears in the **Workflows** list.

<figure><img src="https://884876233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdK3XMLdV8zRg847RmGmZ%2Fuploads%2Fgit-blob-407ec2f70a1839d2fac9ccd1d6eac6ab7fe3676f%2FWF9%20-%20Workflow%20in%20the%20list.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

12. Review the results in **Workflows** > **Execution Logs**.

The execution log shows the workflow status, the number of affected issues, and provides a link to the corresponding **Active Issues**.

<figure><img src="https://884876233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdK3XMLdV8zRg847RmGmZ%2Fuploads%2Fgit-blob-0497dffdebf9b90ea7b7c1a3ffb591f91ecf634c%2FWF10%20-%20Execution%20Log%20(1).png?alt=media" alt="" width="563"><figcaption></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
