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

# Jira

## Step 1: Generate Credentials

1. **Generate API Token**

   * Go to Atlassian API Token Management
     * Click ***Create Token***
     * Label it (e.g., “Alert Integration”) and copy the token

   ![Create API Token](https://4191868192-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOlFHF8fl339QOw3Og8L7%2Fuploads%2Fgit-blob-3ed2fc36394ccdd891579570e20528e3a2e23198%2Fjira-image1.jpg?alt=media)

   * Note down the ***admin email address*** and ***Jira base URL*** (e.g., <https://your-domain.atlassian.net>)
2. **Assign Necessary Permission Scopes**

   * Go to ***Select App***
     * Select ***Jira*** app

   ![Select JIRA App](https://4191868192-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOlFHF8fl339QOw3Og8L7%2Fuploads%2Fgit-blob-376fa6b132f5bdd6fe942618bd2e1d5b070af5de%2Fjira-image2.jpg?alt=media)

   * Go to ***Select Scopes***
     * Select ***write:jira-work***

   ![Assign Permission Scopes](https://4191868192-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOlFHF8fl339QOw3Og8L7%2Fuploads%2Fgit-blob-b82e5cca54192d3e31c2c547ca395300dbc371fe%2Fjira-image3.jpg?alt=media)

   * Review the settings

***

## Step 2: Define JIRA Issue Ticket Fields

1. **Each alert will be converted into a Jira issue with the following fields**

   | Field        | Description                                                                      |
   | ------------ | -------------------------------------------------------------------------------- |
   | project      | Key or ID of the Jira project (e.g., "OPS", "ALERTS" or "10034", "2000")         |
   | issuetype    | Key or ID of type of issue (e.g., "Bug", "Task", "Incident" or "10040", "10000") |
   | reporter     | Atlassian account ID of the reporter (not email)                                 |
   | labels       | Optional: tags like "automated", "alert", "monitoring"                           |
   | customfields | Optional: map alert metadata to custom Jira fields                               |

   * Please use the following to gather more info about the custom fields, if necessary:
     * [Get custom field IDs for Jira](https://confluence.atlassian.com/jirakb/get-custom-field-ids-for-jira-and-jira-service-management-744522503.html)
     * Please note down the ***Custom Field Name*** and the ***text value*** that should be assigned to the custom field.

***

## Deliverables

Please email the following to <support@threatdefence.com>:

1. **API Credentials**
   * Please make sure the following credentials are noted in the email.
     * JIRA\_EMAIL : admin email address
     * JIRA\_API\_TOKEN : generated API token
     * JIRA\_BASE\_URL : Jira base URL noted above
2. **Jira issue ticket fields**
   * Please note the fields needs to be set for the Jira issue ticket
     * project
     * issuetype
     * reporter
     * labels
     * customfields (names & values)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.threatdefence.com/platform-management/alerting/jira.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.