> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tekma.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Send a capture to Linear

> Connect a Linear team and create a link-backed issue with the destination fields your workspace permits.

Linear delivery turns a saved capture into an issue in a team. A workspace owner connects one team as the default. Members send there; owners may choose another team available to the same Linear identity for one issue.

## Requirements and connection

You need workspace-owner permission to connect Linear and capture-edit permission to send. Use **Continue to Linear** for OAuth when available, or **Use a token instead** with an API key that can read the team and create issues. The connection field is **Team ID**, which is a Linear UUID rather than a team display name.

1. Open **Settings → Integrations** and choose **Connect** next to Linear.
2. Choose **Continue to Linear** and authorize the requested access, or choose **Use a token instead** and enter an API key.
3. Enter **Team ID** and choose **Connect Linear**. Tekma checks the team before saving it.
4. Confirm the row says **Connected**. Use **Manage** to change the destination without replacing existing credentials.

## Send an issue

1. Open a saved capture and choose **Send to app → Linear**.
2. Wait for **Loading preview…**. Review the selected team, title, saved description and private capture URL.
3. Choose **Project**, **Assignee**, up to ten existing **Labels**, **Priority**, **Status**, **Cycle**, and **Estimate** when the selected team exposes those fields. Priority options are **No priority**, **Urgent**, **High**, **Medium**, and **Low**. Cycle choices depend on team settings. Estimate choices follow the team's configured scale; Tekma offers zero only when Linear allows it and does not accept an arbitrary point value.
4. Use **Edit visible fields** to hide optional fields, add context, and choose **Send to Linear**.
5. Open the returned issue and confirm each selected value. If the result is unconfirmed, inspect Linear before retrying.

Owners can change **Team** for this send. Changing teams clears projects, assignees, labels, status, cycle and estimate selections. Members cannot switch from the configured team. An alternate team affects this issue only.

| Field    | Supported values                                             |
| -------- | ------------------------------------------------------------ |
| Team     | Configured team; owner-only alternate accessible team        |
| Project  | Project available to the selected team                       |
| Assignee | Active assignee available to the selected team               |
| Labels   | Existing applicable team or workspace labels; maximum 10     |
| Priority | No priority, Urgent, High, Medium, Low                       |
| Status   | Unarchived workflow state for the team                       |
| Cycle    | Unarchived cycle when cycles are enabled for the team        |
| Estimate | Values from the team scale, including zero only when enabled |

The issue contains report text, sanitized source URL, capture kind and a private Tekma link. It does not include video, screenshots, comments, or network logs. Tekma validates the team and all selected IDs immediately before creating the issue and checks the returned issue for dropped metadata.

## Troubleshooting

If the team cannot load, use its UUID and verify the API key/OAuth identity can read it. An empty cycle list can mean cycles are disabled; an absent estimate reflects the team's estimate settings. Archived teams, projects, labels and inactive users are excluded. If a selected value becomes stale, reopen the preview so Tekma can reload it. A network timeout is not a safe retry signal: search Linear by title first.