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

# Jira

{% hint style="info" %}
Adding notification integrations requires admin privileges in groundcover
{% endhint %}

## Generating API Key

To generate your API key, go here: <https://id.atlassian.com/manage-profile/security/api-tokens>, Create a new API Key and copy it.

## Getting Jira Settings

Get your `host` and `projectKey` from your respective board from its URL. For Example: `https://example.atlassian.net/jira/software/projects/rnd/list`

1. host: `https://example.atlassian.net`
2. projectKey: `rnd`

## Create Jira Webhook Integration in groundcover

1. In groundcover, Go to **Settings → Integrations**.
2. Click on Webhook Integration
3. Add webhook integration:
   1. Select your name
   2. Add the following URL, `{host}/rest/api/2/issue?projectKey={projectKey}` based on your host from step 2. For Example:

      ```yaml
      https://example.atlassian.net/rest/api/2/issue?projectKey=rnd
      ```
   3. Using Basic Authentication
      1. User: Enter your jira mail
      2. Password: API key from step 1.
   4. Save

<figure><img src="https://2771001740-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUHgqKYgCiRKdOpWQdi52%2Fuploads%2Fgit-blob-68c8e0fa19d51cc41ba5bcbb1bea37b93c97a03b%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

### Workflow Example

You can see a detailed workflow example to use with your integration, [here](/~/revisions/wppaVAUQcsAgts3lmC6b/use-groundcover/workflows/integration-examples.md#jira-ticket-creation).


---

# 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.groundcover.com/~/revisions/wppaVAUQcsAgts3lmC6b/integrations/workflow-integrations/jira-webhook-integration.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.