> For the complete documentation index, see [llms.txt](https://docs.plextrac.com/plextrac-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plextrac.com/plextrac-documentation/product-documentation/reports/findings/jira.md).

# Creating Jira Tickets

PlexTrac can be integrated with Jira and allow information about findings to be sent to Jira. Visit the [Jira Cloud integrations page](/plextrac-documentation/product-documentation-1/account-management/account-admin/integrations-and-webhooks/integrations-api/jira.md#setting-up-a-jira-integration) for details on setting up Jira. 

{% hint style="info" %}
The PlexTrac to Jira integration supports field content only. Rich text formatting (e.g., bold, italics, bullet points) is not preserved when syncing data to Jira.
{% endhint %}

## Linking a Finding to a Jira ticket

<mark style="background-color:yellow;">Step 1:</mark> Navigate to the **Findings** tab of a report.

<div align="left"><figure><img src="/files/h4WMsBdYOxirKWN5upp3" alt=""><figcaption></figcaption></figure></div>

<mark style="background-color:yellow;">Step 2:</mark> Click the three dots under the "Actions" column of the finding to update.

<div align="left"><figure><img src="/files/EH5ph0HuIcN3RAOtjuLg" alt=""><figcaption></figcaption></figure></div>

<mark style="background-color:yellow;">Step 3:</mark> Click **Link Jira Ticket**.

<div align="left"><figure><img src="/files/q4P1P2dwejjyJF5NH1Vp" alt=""><figcaption></figcaption></figure></div>

<mark style="background-color:yellow;">Step 4:</mark> Select the Jira project and issue to associate the finding with. Click **Create ticket**.

<div align="left"><figure><img src="/files/tPqFsSRkjZ8ZPUo3sZ6C" alt=""><figcaption></figcaption></figure></div>

<mark style="background-color:yellow;">Step 5:</mark> The Jira ticket is now listed under "Linked Ticket."

<div align="left"><figure><img src="/files/5VLaGjaA9L9RHRk0W8uU" alt=""><figcaption></figcaption></figure></div>

Clicking the linked ticket value will open Jira. If mapped by the Admin, the finding date reported value will appear in Jira as a value for "Start Date."&#x20;

<div align="left"><figure><img src="/files/MxkTZZRoKSI9mhhYTYIt" alt=""><figcaption></figcaption></figure></div>

If set up for two-way data flow in integration mapping, updating the start date in Jira will update PlexTrac the next time synchronization occurs.

## Creating a Jira Ticket

<mark style="background-color:yellow;">Step 1:</mark> Navigate to the **Findings** tab of a report.

<div align="left"><figure><img src="/files/N5mih0vG3mTC3cua7lQP" alt=""><figcaption></figcaption></figure></div>

<mark style="background-color:yellow;">Step 2:</mark> Click **Status** under the "Actions" column of the finding used to create a Jira ticket.

<div align="left"><figure><img src="/files/h2CSrYnLzMeZSTo1pWWw" alt=""><figcaption></figcaption></figure></div>

<mark style="background-color:yellow;">Step 3:</mark> Click **Create Jira Ticket & Link.**

<div align="left"><figure><img src="/files/pIix7VmpEgRFPyh3Oh4Z" alt=""><figcaption></figcaption></figure></div>

<mark style="background-color:yellow;">Step 4:</mark> Select the Jira project and issue to link with. Click **Create ticket**.&#x20;

<div align="left"><figure><img src="/files/CdlaKJso54K2E5SoVVc3" alt=""><figcaption></figcaption></figure></div>

A ticket in Jira is created, and the ticket number is listed under "Linked Ticket" on the **Findings** tab.

<div align="left"><figure><img src="/files/gTkYdfqASQdOa4xygOit" alt=""><figcaption></figcaption></figure></div>

## Unlinking a Jira Ticket

<mark style="background-color:yellow;">Step 1:</mark> Navigate to the **Findings** tab of a report.

<div align="left"><figure><img src="/files/N5mih0vG3mTC3cua7lQP" alt=""><figcaption></figcaption></figure></div>

<mark style="background-color:yellow;">Step 2:</mark> Click the three dots under the "Actions" column of the finding linked to a Jira ticket.

<div align="left"><figure><img src="/files/h2CSrYnLzMeZSTo1pWWw" alt=""><figcaption></figcaption></figure></div>

<mark style="background-color:yellow;">Step 3:</mark> Click **Unlink Jira ticket.**

<div align="left"><figure><img src="/files/CV1iX8XYpwvaqgkyBgYc" alt=""><figcaption></figcaption></figure></div>

<mark style="background-color:yellow;">Step 3:</mark> A modal appears, confirming the action. Click **Ok**.

<div align="left"><figure><img src="/files/PqUpbVdSHfgoUthAQ3xT" alt=""><figcaption></figcaption></figure></div>

## Bulk Creating Jira Tickets

<mark style="background-color:yellow;">Step 1:</mark> Navigate to the **Findings** tab of a report.

<div align="left"><figure><img src="/files/D2nWmkWY8VAbkehoJtt7" alt=""><figcaption></figcaption></figure></div>

<mark style="background-color:yellow;">Step 2:</mark> Select the desired finding(s) by clicking the check box of the finding row.

<div align="left"><figure><img src="/files/3RO2neVGh2u9nzMfkOGe" alt=""><figcaption></figcaption></figure></div>

<mark style="background-color:yellow;">Step 3:</mark> Hover over the "Actions" button to bring up the pulldown menu and click **Create Jira Tickets**.

<div align="left"><figure><img src="/files/qXSBa3wH0cxVCLuOhGie" alt=""><figcaption></figcaption></figure></div>

<mark style="background-color:yellow;">Step 4:</mark> Select the Jira project and issue type to which the finding(s) should be assigned. Click **Create ticket**.

<div align="left"><figure><img src="/files/Vz1XvVuFbjHNV0uT3zHe" alt=""><figcaption></figcaption></figure></div>

<mark style="background-color:yellow;">Step 5:</mark> A message will confirm that ticket(s) were created, and the linked ticket number will now be displayed for finding on the page.&#x20;

<div align="left"><figure><img src="/files/S2LWrZfk4vNmiNcAt5gG" alt=""><figcaption></figcaption></figure></div>

Clicking the linked ticket value will take you directly to Jira for viewing.&#x20;


---

# 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.plextrac.com/plextrac-documentation/product-documentation/reports/findings/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.