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

# Jira

Send any bug report or recording to Jira in a few clicks.

Screendesk adds the capture link and debugging context automatically.

{% hint style="info" %}
This page covers the manual **Send to app** action. Folder automations create issues automatically when recordings or bug reports enter a folder.
{% endhint %}

### Before you start

* You need edit access on the Screendesk item.
* Connect Jira from **Profile → Integrations**.
* Each teammate uses their own Atlassian account.

### Connect Jira

{% stepper %}
{% step %}

### Open integrations

In Screendesk, go to **Profile → Integrations**.
{% endstep %}

{% step %}

### Connect Jira

Find **Jira** and click **Connect**.

Approve Screendesk in Atlassian.
{% endstep %}

{% step %}

### Return to Screendesk

Jira now appears in your connected apps list.

You can also start this flow from **Send to app → Connect Jira**.
{% endstep %}
{% endstepper %}

### Create a Jira issue

{% stepper %}
{% step %}

### Open the item

Open the bug report or recording in Screendesk.

Click **Send to app**.
{% endstep %}

{% step %}

### Choose Jira

Select **Jira issue**.

If Jira is your only connected app, the main button may say **Send to Jira**.
{% endstep %}

{% step %}

### Review fields

Check the summary and description.

Choose a **Project** and an **Issue type**.

Optionally add a priority and labels.
{% endstep %}

{% step %}

### Create the issue

Click **Create issue**.

Screendesk keeps the Jira issue link on the item, even if you disconnect later.
{% endstep %}
{% endstepper %}

### Available fields

| Field       | Required | Notes                                              |
| ----------- | -------: | -------------------------------------------------- |
| Summary     |      Yes | Used as the Jira issue summary.                    |
| Description |      Yes | Your notes are added above the Screendesk context. |
| Project     |      Yes | The Jira project where the issue will be created.  |
| Issue type  |      Yes | Issue types load after you choose a project.       |
| Priority    |       No | Priorities load from Jira.                         |
| Labels      |       No | Labels load from Jira.                             |

### What Screendesk sends

* A direct link to the bug report or recording
* The source website URL, when available
* Device and browser details
* The capture timestamp in UTC
* A link to developer information in Screendesk

Anything you add in the description goes above the generated Screendesk context.

### Customize the form

Click **Edit fields** in the Jira modal to show or hide optional fields.

Required fields stay visible.

Your field choices are saved for your Jira connection.

### Permissions

* You must be able to edit the bug report or recording.
* Watch-only users cannot connect personal app accounts or send items to Jira.
* Workspace admins can remove Jira from **Profile → Integrations** for the whole workspace. Existing issue links stay visible.

<details>

<summary>Troubleshooting</summary>

**Jira is not in the Send to app menu**

Open **Profile → Integrations** and connect Jira.

If the button is missing entirely, confirm that you can edit the bug report or recording.

**No Jira site is available**

Make sure your Atlassian account has access to at least one Jira Cloud site.

Then reconnect Jira from **Profile → Integrations**.

**Projects, issue types, priorities, or labels do not load**

Reconnect Jira and make sure your Atlassian account has permission to browse the Jira project and create issues in it.

</details>


---

# 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.screendesk.io/bug-reports/send-to-apps/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.