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

# Jira Software

## How works the connection HackenProof -> Jira <a href="#h_51c5ea38c0" id="h_51c5ea38c0"></a>

HackenProof uses a ticket-based system that has [different stages of reports](/bug-bounty/reports-basics.md) processing. And when the report is considered valid, it proceeds to the TRIAGED stage.

We believe the company may need to connect its HackenProof bounty program to its Jira to work on valid reports to fix them.

* Once you connect your bounty program to Jira, it will create a Jira project with the same name as your HackenProof bug bounty program.
* Then, all reports that are marked as TRIAGED will appear in your Jira project.

<mark style="background-color:purple;">Note #1. Only reports with state TRIAGE will appear in the Jira</mark>

<figure><img src="https://downloads.intercomcdn.com/i/o/642795709/80c26de318aa2c6aa582f505/image.png" alt=""><figcaption></figcaption></figure>

## How to manage reports in Jira <a href="#h_d67a79a8be" id="h_d67a79a8be"></a>

The report/ticket management process and the type of boards you intend to use in Jira depend on your team.

For example, it can be a Kanban board with the following flow:

<figure><img src="https://downloads.intercomcdn.com/i/o/604627300/6870bf3e11640a30eedc1003/image.png" alt=""><figcaption></figcaption></figure>

## After you fix the reports <a href="#h_ae9f442195" id="h_ae9f442195"></a>

Please remember, after developers fix the report, it must be manually marked as RESOLVED in your HackenProof program.

<figure><img src="/files/TiDYdVh0SvktwC3iCu1p" alt=""><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 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.hackenproof.com/welcome/integrations/jira-software.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.