> 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/helpdesk-integrations/jira-service-management/install-and-set-up.md).

# Install and set up

Install the Screendesk app from the Atlassian Marketplace, connect your Jira site to your workspace, and choose its settings.

You need to be a Jira admin, and an admin of your Screendesk workspace.

{% embed url="<https://app.screendesk.io/recordings/edacf820-e496-4451-a90b-9966c0d7a185>" %}

1. In Screendesk, go to **Settings → Integrations** and click **Connect** on the **Jira Service Management** card. The **Connect Jira** dialog has the steps below. Click **Open the Marketplace**.
2. On the [Screendesk app's Marketplace page](https://marketplace.atlassian.com/apps/1238221/screendesk-screen-recording?hosting=cloud\&tab=overview), click **Get it now** and install it in your Jira site.
3. Open any request in Jira Service Management and click the **Screendesk** icon in the row of buttons under its title. The Screendesk panel opens further down the request, above **Activity**.
4. Click **Connect** in the panel, signed in to Screendesk as an admin. Jira asks before it opens an external page: click **Continue**. On the Screendesk page, **Connect** followed by your site's name, check the workspace it names and click **Connect Jira**.
5. Go back to Jira. The panel, which said **Waiting for Screendesk…**, shows Screendesk's actions, for everyone on your team.

The Jira Service Management card in **Settings → Integrations** then shows the Jira site it's connected to. A Jira site can be connected to one Screendesk workspace only. The link from the panel works for an hour: if it expires, click **Connect** in the panel again.

## Settings

Click **Configure** on the Jira Service Management card. The settings follow the way a recording travels.

**Ask from an issue**

* **Recordings in the panel**: what agents see under the actions, the customer's recordings (**From this customer**) or the issue's (**On this issue**).

**Let customers record on their own**

* **Record on the customer portal**: a **Record your screen** button on the portal's request forms. See [Customer portal](https://docs.screendesk.io/helpdesk-integrations/jira-service-management/customer-portal.md).

**When a recording arrives**

* **Add requested recordings to the issue**: recordings from the links agents copy in the panel are added to their issue. Off, the customer gets a link to paste in the request themselves.
* **Add portal recordings to the request**: recordings made on the portal's request form are added to the request.
* **Comment**: how Screendesk adds them, as an **Internal note** for your agents or a **Reply to customer**.
* **Label the issues**: Screendesk labels the issues it works in, such as `screendesk-recording-requested` and `screendesk-recording-received`, so you can filter and report on them in Jira.

Screendesk adds recordings to issues as the app itself: no admin email or API token is needed.

## Uninstall

1. In Atlassian Administration, go to **Site settings → Connected apps**, open Screendesk, click **View app details**, then **Uninstall**. In Jira, **Settings → Apps** takes you there.
2. In Screendesk, click **Disconnect** on the Jira Service Management card.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.screendesk.io/helpdesk-integrations/jira-service-management/install-and-set-up.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
