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

# Jira Inbound Integration

The ilert integration for Jira helps you to easily connect ilert with Jira.

[Jira](https://www.atlassian.com/software/jira) is an issue-tracking product developed by Atlassian that allows teams to manage, track, and prioritize their work. It's extensively used for bug tracking, issue tracking, and agile project management. Jira provides customizable workflows, real-time collaboration capabilities, and a variety of integrations with other tools, making it a popular choice for development teams and project managers in various industries.

With the ilert Jira integration, you can create alerts in ilert based on Jira issues.

## In ilert: Create a Jira alert source <a href="#in-ilert" id="in-ilert"></a>

1. Go to **Alerting** → **Alert sources** and click **Create new alert source**.
2. Search for **Jira**, click its tile, and click **Next**.
3. Give your alert source a name, optionally assign teams, and click **Next**.
4. Choose who gets notified: select **Use existing escalation policy** and pick a policy, or **Generate new escalation policy** to start with a basic one that notifies you first. Click **Next**.

   <figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2Fgit-blob-8a281bf3931f5a1a531951ce97984d50989dd875%2Falert-source-escalation-step.png?alt=media" alt="The escalation step of the ilert alert source wizard, headed Who should be notified about alerts, with an escalation policy selected and a preview of its escalation rules below."><figcaption><p>Pick an existing escalation policy, or generate a basic one without leaving the wizard.</p></figcaption></figure>
5. Select **Default grouping** and click **Continue setup**. It groups events by the alert key the integration sets; the other [grouping options](/alerting/configure-alerting/alert-sources.md#event-grouping) are easier to judge once events are arriving.
6. The next page shows more settings, such as notification priority and alert templates. Click **Finish setup** for now; you can change them later.
7. On the final page, ilert shows the integration key and URL for this alert source. You will need them later in this guide.

## In Jira: Create the webhook <a href="#in-topdesk" id="in-topdesk"></a>

{% hint style="info" %}
You need admin permissions to manage Jira webhooks.
{% endhint %}

1. Go to Jira and then to **System** **Settings:**

![](https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76ygPnS4HUcFSX8ulm%2F-MLdjckXQ7TBi72o3Dt5%2F-MLdlKiw-sWxz6XXPFlX%2FProjects_-_Jira.png?alt=media\&token=9bd30753-c1b6-42b1-a9ef-97f4fad216c1)

2. Click on the **WebHooks** and then on the **Create a WebHook** button to add a new webhook for ilert

![](https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76ygPnS4HUcFSX8ulm%2F-MLdjckXQ7TBi72o3Dt5%2F-MLdm0jWuRmgZQV2sQxm%2FWebHooks_-_Jira.png?alt=media\&token=f0327a0a-4921-4f1b-98fd-7380a50ed533)

3. On the next page, in the section **Name** field, enter a name (e.g. ilert). In the section **URL** field, paste the **Webhook URL** that you generated in ilert. In the section **Issue** choose **created**, **updated** and **deleted** events.

![](https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76ygPnS4HUcFSX8ulm%2F-MLdjckXQ7TBi72o3Dt5%2F-MLdql_0QQeQ8XRrohiK%2FWebHooks_-_Jira.png?alt=media\&token=0b4441c0-1169-4c1b-a154-b4379733ae68)

4. Scroll down and make sure that the request body is **not excluded**

![](https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76ygPnS4HUcFSX8ulm%2F-MkHN-zlos91l4ep0Iyd%2F-MkHN_c4E0h6-vPCyMMQ%2FScreenshot_23_09_21__13_18.png?alt=media\&token=723b94bd-c8e9-497e-890b-6b4f003ecd68)

5. Scroll to bottom and click on the **Create** button

## FAQ <a href="#faq" id="faq"></a>

**Will alerts in ilert be resolved automatically?**

Yes

**When will alerts be resolved?**

Alerts are resolved with the resolution event of a Jira ticket. *(Note: ticket status transition alone will not resolve an alert)*

**Will alerts in ilert be accepted automatically?**

No, unfortunately, Jira events are not compatible with ilert accepted event.

**Can I connect Jira with multiple alert sources from ilert?**

Yes, simply create more webhooks in Jira.

## Related articles

{% content-ref url="/pages/-MLHaD9Yxxo4AAbA8nu4" %}
[Jira Outbound Integration](/integrations/outbound-integrations/jira.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.ilert.com/integrations/inbound-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.
