> For the complete documentation index, see [llms.txt](https://docs.r.xyz/main/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.r.xyz/main/bug-bounty/organizations/bb-settings/integrations/jira.md).

# Jira

Organization Admin users can integrate Remedy with their Jira to automatically open tickets for valid reports in the designated Jira project.

## How Jira integration works

Once a report is validated by the Remedy Traige Team, a task-type Jira ticket is automatically generated for the selected Jira project.

Each ticket is enriched with detailed information about the report for streamlined issue tracking. This includes the report title, asset type, asset URL, report URL, reported date, report content (as the ticket description), and severity of the report applied as a Jira label.

## **Setup Process**

1. **Access Integration Settings**

\> Navigate to Bug Bounty Settings > [Integrations tab.](https://hunt.r.xyz/bb-settings/integrations)\
\> Locate the Jira Integration widget, which includes:

2. **Connect Jira**

\> Click Connect to initiate the Jira authorization and connection flow.\
\> Choose the Remedy program from which reports will generate Jira tickets.\
\> Select the Jira project where these tickets will be opened.

{% hint style="info" %}
Note that by connecting to Jira, you agree to share report-related data for issue tracking and management.
{% endhint %}

To Add a connection, please follow the following steps 

\> Locate the Jira integration widget \
\> Click "Add new connection."

To **Disconnect Jira,** please follow the following steps

\> Locate the Jira integration widget \
\> Click "Disconnect all" **or** click "Disconnect" for the specific connection\
\> Confirm disconnection:

Once disconnected, Jira will no longer receive any tickets from Remedy.


---

# 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.r.xyz/main/bug-bounty/organizations/bb-settings/integrations/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.