> 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 apps

Create Linear, GitHub, and Jira issues from a recording.

Turn a recording into an issue without losing context. Screendesk creates the issue and keeps a visible link on the recording.

Use **Send to apps** when a recording becomes a bug, task, or investigation for your engineering team.

{% hint style="info" %}
This section covers the manual **Send to app** action. If you want automatic issue creation, use folder automations instead.
{% endhint %}

### Choose an app

<table data-view="cards"><thead><tr><th>App</th><th data-card-target data-type="content-ref">Guide</th></tr></thead><tbody><tr><td>Linear — create issues with team, project, status, assignee, and labels.</td><td><a href="/request-screen-recording/send-to-apps/linear.md">Linear</a></td></tr><tr><td>GitHub — create issues in a repository with labels, assignees, and milestones.</td><td><a href="/request-screen-recording/send-to-apps/github.md">GitHub</a></td></tr><tr><td>Jira — create issues with project, issue type, priority, and labels.</td><td><a href="/request-screen-recording/send-to-apps/jira.md">Jira</a></td></tr></tbody></table>

### How it works

{% stepper %}
{% step %}

### Connect your app

Each teammate connects apps from **Profile > Integrations**. Screendesk uses that person's account and permissions in the destination app.
{% endstep %}

{% step %}

### Open the recording

Open the recording you want to share. Then click **Send to app**.
{% endstep %}

{% step %}

### Create the issue

Choose the destination app. Review the title and description. Fill in the app-specific fields. Then create the issue.
{% endstep %}
{% endstepper %}

### Before you start

* Connect the app from **Profile > Integrations**.
* Make sure you can edit the recording.
* Make sure your connected account has access to the target project or repository.

### What Screendesk sends

Every created 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 create issues.


---

# 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.