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

# Jira

Connect BugBug to Jira to create issues from failed test runs and keep links between the issue and its test run.

BugBug's Jira integration lets you create Jira issues from failed test runs.

Use this integration when a failed BugBug test needs follow-up work in Jira. The issue includes run context, so your team does not have to copy it by hand.

{% hint style="warning" %}
The Jira integration requires the Business plan. See [BugBug pricing](https://bugbug.io/pricing/) for details.
{% endhint %}

## Connect Jira with BugBug

1. Go to the **Integrations** page.
2. Find **Jira** on the integrations list.
3. Click **Manage**.
4. Click **Connect**.
5. Authorize BugBug in Atlassian.
6. Select the Jira site you want to connect.
7. After authorization, you will return to BugBug.

BugBug uses the connection to read available Jira projects and create issues in the selected project.

## Create a Jira issue from a failed test

1. Open the failed test run.
2. Find the failed test or step that should become a Jira issue.
3. Choose **Create Jira issue**.
4. Select the Jira project.
5. Edit the issue title if needed.
6. Confirm issue creation.

BugBug creates the Jira issue and links it to the test run. You can open the issue from BugBug later.

BugBug does not automatically create Jira issues for every failed scheduled run. Create the issue when the failed run needs work in Jira.

## View or remove linked Jira issues

Linked Jira issues are shown in BugBug next to the related failed run, test, or step.

If an issue was created by mistake or no longer belongs to the run, you can remove the link from BugBug. Removing the link in BugBug does not delete the issue in Jira.


---

# 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.bugbug.io/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.