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

# Jira

We support Jira as an alerting destination.

{% stepper %}
{% step %}

#### Create a Jira API token

1. Create an API token [here](https://id.atlassian.com/manage-profile/security/api-tokens)
2. Set the maximum **expiration date** of 365 days
3. Set **scopes**:
   1. `read:jira-user`
   2. `read:jira-work`
   3. `write:jira-work`
4. Select **create** and save the API token securely See Atlassian's [API token documentation](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/) for API token setup.
   {% endstep %}

{% step %}

#### Setup Jira Integration

Under Policy Maker, select the Jira integration and input the following:

1. **User Email:** the e-mail associated with the API token
2. **Api Key**: the API token saved in the previous step
3. **Base Url:**
   * For a token with scopes, including a service-account token, use `https://api.atlassian.com/ex/jira/{cloudId}`. Do not use the Jira tenant URL for this token type.
   * For a token without scopes, use the URL for your Jira tenant, e.g., `https://customerName.atlassian.net`
     {% endstep %}

{% step %}

#### Add Jira notifications as an action

1. Create or edit a policy, and **Add automated actions**
2. Add an action to **Create a Jira ticket**
3. Provide the **Project Key**, **Issue Type**, **Assignee**, **Reporter**, and any **custom fields**. Ensure that the user has access to the project and that the fields exist for the Project and Issue Type.
   {% endstep %}
   {% endstepper %}

{% hint style="warning" %}
It is recommended to add Jira notifications after a policy has been created and the initial violations populated. A ticket is created per violation, so ensure that policies are sufficiently scoped.
{% endhint %}