> 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.md).

# Send to Linear, GitHub or Jira

Create a Linear, GitHub or Jira issue from a recording or bug report, with your own account.

Turn a recording or bug report into an issue. Screendesk creates it with your own account and keeps the issue link on the recording, even if you disconnect later.

{% embed url="<https://app.screendesk.io/recordings/a1af03c5-634e-4eec-b39d-ba6f38a9ac78>" %}

This page covers sending by hand. To create issues automatically, use [automations](https://docs.screendesk.io/organization-and-workflows/workspace-automations.md).

### Connect your account

Each teammate connects their own account, so issues are created with their permissions.

1. Click your avatar → **Connected apps**.
2. Click **Connect** on **Linear**, **GitHub** or **Jira**, and approve Screendesk on that app's screen.
3. Jira only: if your Atlassian account reaches several sites, pick the one Screendesk should use under **Create issues on**.

<figure><img src="https://3820804400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfW6XSzJSKsNyZnOkSJPt%2Fuploads%2FltjHdwNmd3gzo3esGGE9%2Fdocs-panel-connected-apps.png?alt=media" alt="Connected apps in personal settings"><figcaption></figcaption></figure>

You can also connect from a recording: open the **Send to app** menu and choose **Connect Linear**, **Connect GitHub** or **Connect Jira**.

If an app shows **Action required**, click **Reconnect**.

### Create an issue

1. On the recording, click **Send to app**. Once an app is connected, the button names it, for example **Send to Linear**. The arrow next to it lists the others: **Linear issue**, **GitHub issue**, **Jira issue**.
2. Fill in the form and click **Create**.

| App    | Required                     | Optional                                                               |
| ------ | ---------------------------- | ---------------------------------------------------------------------- |
| Linear | Title, Team                  | Description, Project, Parent issue, Priority, Assignee, Status, Labels |
| GitHub | Title, Repository            | Description, Labels, Assignees, Milestone                              |
| Jira   | Summary, Project, Issue type | Description, Priority, Labels                                          |

**Edit fields** in the form shows or hides the optional fields. Lists like projects, labels and assignees come from your account in that app.

Below your description, Screendesk adds a link to the recording, the website URL, the device and browser, the date and time in UTC, and a link to the developer information.

### Who can send

Anyone who can edit the recording: its owner, Admins and Editors. Watch-only members can't connect apps or send.

In **Connected apps**, **Disconnect app** removes your own connection. Admins also see **Remove app from workspace**, which disconnects the app for everyone. Automations keep their own connection, and existing issue links stay on their recordings.


---

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