> 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/request-screen-recording/send-to-apps/jira.md).

# Jira

Create a Jira issue from any recording you can edit. The issue includes a link back to Screendesk and the context your team needs to reproduce and prioritize the problem.

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

### Before you start

* Connect Jira from **Profile > Integrations**.
* Make sure your Jira account can access the target site and project.
* Make sure you can edit the recording.

### Connect Jira

Jira is connected from your personal Screendesk profile. Each teammate sends issues with their own Jira account and project permissions.

1. In Screendesk, open **Profile > Integrations**.
2. Find **Jira**.
3. Click **Connect**.
4. Approve Screendesk on Atlassian's authorization screen.
5. Return to Screendesk. Jira now appears in the connected apps list.

If you open the **Send to app** menu before connecting Jira, choose **Connect Jira** from the menu and complete the same authorization flow.

### Create the issue

{% stepper %}
{% step %}

### Open the recording

Open the recording in Screendesk. Then 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 %}

### Fill in the fields

Choose a **Project** and **Issue type**. Review the title and description. Then add any optional fields you need.
{% endstep %}

{% step %}

### Create the issue

Click **Create issue**. Screendesk adds the Jira issue link to the recording.
{% endstep %}
{% endstepper %}

The issue link stays visible even if Jira is disconnected later.

### Available fields

| Field       | Required | Notes                                              |
| ----------- | -------: | -------------------------------------------------- |
| Title       |      Yes | Used as the Jira issue summary.                    |
| Description |      Yes | Your notes are added above the Screendesk context. |
| Project     |      Yes | Determines where the issue is created.             |
| Issue type  |      Yes | Available issue types update by project.           |
| Priority    |       No | Available priorities come from Jira.               |
| Labels      |       No | Labels are added to the created Jira issue.        |

### What Screendesk adds

Every issue includes:

* A direct link to the recording
* The source website URL, when available
* Device and browser information
* The recording timestamp in UTC
* A link back to developer information in Screendesk

Anything you type in the description appears before the generated Screendesk context.

### Permissions

You must be able to edit the recording to use **Send to app**. Watch-only users cannot connect personal app accounts or send recordings to Jira.

Workspace admins can remove Jira from the workspace from **Profile > Integrations**. This disconnects Jira for everyone in the workspace, but existing Jira issue links stay on their Screendesk recordings.

### Troubleshooting

<details>

<summary>Jira is not in the Send to app menu</summary>

Open **Profile > Integrations** and connect Jira. If the button is missing entirely, confirm that you can edit the recording.

</details>

<details>

<summary>Jira asks you to reconnect</summary>

Reconnect Jira from **Profile > Integrations**. This can happen if Atlassian revokes the token or the connection expires.

</details>

<details>

<summary>Projects, issue types, priorities, or labels do not load</summary>

Reconnect Jira and make sure your Jira account has access to the site, project, and issue fields you want to use.

</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/request-screen-recording/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.