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

# Jira

#### What it does

With the Jira integration, Birdie users can:

* create a new Jira issue from a recording
* add a comment to an existing issue from a recording
* choose the target project (and the issue, when commenting)
* set the issue type, and optionally an assignee, priority and labels
* include the Birdie recording link and context in the issue

This makes it easier to turn customer recordings into actionable issues for engineering and product teams.

{% hint style="info" %}
This is the **Jira Cloud** (issue tracker) integration. It's separate from the Jira Service Management (helpdesk) integration — you can connect either or both.
{% endhint %}

#### How it works

A Birdie admin connects Jira once for the whole workspace.

After that, anyone in the Birdie workspace with access to the feature can use **Send to Jira** from a recording.

This means individual users do **not** need to connect their own Jira account to create issues from Birdie.

#### How to connect Jira

1. Open your Birdie workspace settings.
2. Go to the **Integrations** section.
3. Click **Connect** on the Jira card.
4. Authorize the Birdie app on Atlassian.
5. Choose the Jira **site** you want Birdie to access, then accept.

Once connected, Birdie will be able to create issues in the projects on that Jira site.

#### How to create an issue

1. Open a recording in Birdie.
2. Click **Send to Jira**. (If you also have Linear, ClickUp or GitHub connected, use the arrow next to the **Send to** button and pick **Send to Jira**.)
3. Fill in the details:
   * Project (required)
   * Issue — leave as **Create a new Issue**, or pick an existing issue to comment on it instead
   * Type — the issue type (required when creating a new issue)
   * Assignee
   * Priority
   * Labels
   * Title (required when creating a new issue)
   * Description
4. Click **Create New Issue** (or **Comment on Issue** when an existing issue is selected).

Birdie will create the issue (or comment) in Jira and include the recording context.

#### What is included in the Jira issue

Depending on how you fill in the form, Birdie can include:

* the issue summary (title)
* your description
* a link to the recording (Watch on Birdie)
* context data (browser, OS, timezone, location, date)
* the issue type, assignee, priority and labels selected in the form

{% hint style="info" %}
Jira can't play the recording inside an issue, so Birdie adds a clickable **Watch on Birdie** link that opens the recording.
{% endhint %}

#### Disconnecting Jira

1. Open the Jira card in **Integrations** and click **Disconnect**. This removes the stored connection, so Birdie stops using Jira.
2. Atlassian has no way to signal an app removal back to Birdie, so after disconnecting click **Revoke at Atlassian** (or go to **id.atlassian.com → Connected apps**) and remove the Birdie app there.

#### Notes

* A Birdie admin must connect Jira before other users can use the integration.
* The available projects, issue types, assignees, priorities and labels depend on the connected Jira site and on your Jira permissions.
* If a project requires fields that aren't in the form (for example a mandatory custom field), Jira will reject the issue and Birdie shows Jira's own error so you know which field is missing.
* Unlike some integrations, Jira does **not** notify Birdie when access is revoked. If you revoke Birdie in Atlassian without disconnecting in Birdie first, the card may still appear connected until the next attempt to create an issue fails.