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

# Jira

{% hint style="info" %}
This integration is currently in beta.
{% endhint %}

## Connect Atlassian Jira

* Visit your *Settings → Integrations →* [Add](https://app.halosecurity.com/user/settings/integrations/add).
* Add the Jira integration.
* Add a name for your integration.
* Click **Connect Now.**
* You'll be redirected to Jira to approve permissions.

## Create Profiles

After connecting Jira, you can create profiles to control how tickets are created. To create a profile:

1. Navigate to the **Profiles** tab
2. Click the **+** icon
3. Enter a name for the profile
4. Configure your settings:
   1. **Project:** The Jira Project where tickets will be created.
   2. **Reported By**: The reporter for the created tickets.
   3. **Assigned To**: The assignee of the created tickets.
   4. **Priority:** The priority of the created tickets.
   5. **Issue Type:** The type of the created tickets.
   6. **Due Date Days**: The number of days from now when the ticket is due.
   7. **Labels:** Labels for the created tickets.
5. Click **Save**

## Create Tickets

### Manually Create Tickets for Individual Issues

When viewing an [Issue](/docs/platform/issues.md), you can easily create an individual ticket for the issue.

1. Click the **Plug icon** in the top right
2. Select the Profile you'd like to use
3. Make any adjustments to the ticket details
4. Click **Create Ticket**

### Automatically Create Tickets for Issues

To create tickets for issues, we recommend using Automations.;

* Navigate to *Scan → Settings →* [Automations](https://app.halosecurity.com/user/settings/automations/)
* Create a filter with the type as **Target Issue**
* Apply the profile you created as an action

Learn more about Automations:

{% content-ref url="/pages/iq99K8aC1ETIXaLg4FrK" %}
[Automations](/docs/platform/automations.md)
{% endcontent-ref %}

### Automatically Create Tickets for Additional Events

Event rules allow you to create a Jira ticket for Halo Security events beyond issues. For example, you can create a Jira ticket when a new port is opened or a new target is added.

To receive Jira tickets, create Event Rules and add your Jira profile as an action.

Visit *Events →* [Event Rules](https://app.halosecurity.com/user/settings/event-rules/) to set up rules that determine which events created Tickets in Jira.

Learn more about configuring Event Rules:

{% content-ref url="/pages/QVrCXwRcuy8YWA5L25VR" %}
[Event Rules](/docs/platform/events/alerts.md)
{% endcontent-ref %}


---

# 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.halosecurity.com/docs/integrations/workflow-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.