# Jira

BugSplat's Jira integration allows your team to create defects with a few clicks. Links from BugSplat to Jira allow for quick navigation from defects to crash reports. Defects created from BugSplat automatically include symbolic call stack information and other crash-specific data.

### Integrating Jira and BugSplat

1. Login to your account.
2. Click the Gear icon (⚙️) at the top right of the page and navigate to the [Database Settings](https://app.bugsplat.com/v2/database/integrations) page, and under **Database > Integrations >** **Defect Tracker**, select **Jira** from the options shown.
3. Enter your **Username**, **Token**, **URL**, and **Issue Type** into the appropriate boxes. For Jira Cloud, use an [API Token](https://id.atlassian.com/manage-profile/security/api-tokens) in the **Token** field. For self-hosted Jira Server use your account's password for the **Token** field.
4. Click **Apply**.
5. Once a connection to Jira has been established, you can select one of your projects from the project dropdown list.
6. After selecting your desired project, click **Apply** again.
7. Add additional data in any of the other fields.

{% hint style="info" %}
The optional **Assignee ID** field requires the Atlassian user ID when using Jira Cloud. Jira Server doesn't support user IDs, so use the user name.
{% endhint %}

### Creating an Issue in Jira

1\. Create a new defect from the crashes page or a [stack key](https://docs.bugsplat.com/education/bugsplat-terminology#stack-key) page by using the **Create Defect** button.

2\. Enter relevant details and click the **Submit** button to create the defect. You can also enter an existing **Defect ID** if you'd like to associate a crash or stack key with an existing defect from Jira.

3\. Click the link to view the new Jira issue created by BugSplat.

<figure><img src="https://976110677-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LBMgmIcgkIXSUfnXDSv%2Fuploads%2FQpCWRBH4KNq00fOXIMaC%2Foutput.gif?alt=media&#x26;token=e5d8bc98-3858-4484-bcbe-4ad65b4bd65c" alt=""><figcaption><p>Create a Jira Issue with BugSplat</p></figcaption></figure>

### Bi-Directional Status Syncing

BugSplat can listen to status updates on issues from Jira and update a defect group's status accordingly. Similarly, when a defect group's state is updated in BugSplat, the update can be pushed to Jira, which allows the two systems to stay synchronized.

To configure bi-directional Jira synchronization, perform the following steps:

1. Create a Jira System webhook via **⚙️ > System > WebHooks**
2. Set the WebHook URL value to `https://app.bugsplat.com/api/webhook/jira.php?database=your-bugsplat-database`, being sure to use the name of your BugSplat database
3. Generate a **WebHook Secret** and copy the secret value
4. Configure the webhook to emit events for **Issue Updated**
5. Navigate to BugSplat's [Defect Tracker Integration](https://app.bugsplat.com/v2/database/integrations#defect-trackers) page
6. Enter values for **Webhook Secret**, **Open Status**, and **Closed Status**

You can test the integration by linking a Jira issue to a BugSplat defect. Set the BugSplat status to Open or Closed. When the status changes in BugSplat, the Jira status should be set to the value you entered for **Open Status** and **Closed Status,** respectively.

### Automated Defect Creation

Want to create issues in Jira automatically for each new crash or crash group? Check out the document on auto-creating defects in your third-party defect tracker tool [here](https://docs.bugsplat.com/introduction/development/integrating-with-tools/issue-trackers/automatic-issue-creation).


---

# Agent Instructions: 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:

```
GET https://docs.bugsplat.com/introduction/development/integrating-with-tools/issue-trackers/jira.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.