> For the complete documentation index, see [llms.txt](https://docs.akto.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akto.io/api-security-testing/how-to/auto-create-jira-tickets.md).

# Auto-Create Jira Tickets

Akto makes it simple to automate your issue tracking process by allowing **auto-creation of Jira tickets** whenever security tests are run. This ensures that any vulnerabilities or issues found during your tests are automatically logged in Jira, helping your team stay on top of critical fixes without manual intervention.

<figure><img src="/files/hZ5PIM1KwRT0J0Ty69FA" alt=""><figcaption></figcaption></figure>

### How It Works

When setting up a test run in Akto, you will see the option to **Auto-create tickets**. Once enabled, Akto will automatically create Jira tickets based on the vulnerabilities detected.

#### Configuration Options

* **Environment Selection:** Choose the environment (e.g., PROD, DEV) where the test is being executed.
* **Ticket Type:** Define the type of Jira ticket to be created (e.g., Task, Bug, Story).
* **Severity Filter:** Specify the severity levels (e.g., Critical, High) for which tickets should be automatically generated.

### Benefits

* **Seamless Integration:** Automatically log issues in Jira without manual effort.
* **Real-Time Tracking:** Ensure vulnerabilities are tracked as soon as they're discovered.
* **Customizable:** Configure ticket types, environments, and severity filters to fit your workflow.

### Important Notes

* Make sure your Jira integration is properly set up in Akto before using the auto-create feature.
* Tickets are only created for the severity levels you specify, helping avoid unnecessary clutter in your Jira backlog.

### Need Help Setting Up Jira Integration?

Check out our step-by-step guide to set up Jira integration here: [Jira Integration Guide](https://docs.akto.io/issues/how-to/jira-integration)


---

# 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.akto.io/api-security-testing/how-to/auto-create-jira-tickets.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.