> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/integrations/ticketing/linear.md).

# Linear

Link customer issues in Pylon to issues in Linear

## Setup

Click into the App Directory from your Pylon dashboard and then click on the Linear integration to view setup instructions.

## [​](https://docs.usepylon.com/product-ticketing/linear#usage)Usage <a href="#usage" id="usage"></a>

### Creating Linear Issues <a href="#creating-tickets" id="creating-tickets"></a>

You can create a Linear issue via the Kanban board or via the triage channel.

1. Via Kanban: From a Pylon issue, you’ll see a Linear Details module in the sidebar. Select the team you’d like to create the ticket in, and click Create.

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2FeAmuT7NEvoQnkpQwcySY%2FCleanShot%202025-10-31%20at%2014.27.19%402x.png?alt=media&amp;token=14801b1b-fbf3-4622-9776-e075deaff53c" alt="" width="375"><figcaption></figcaption></figure>

2. Via Triage channel: when conversational tickets are posted in your triage channel and product ticketing is enabled, you’ll see a `Create Ticket 📦` button.

Clicking it will allow you to select with Linear project to create the issue in, along with a pre-filled AI generated title.

<figure><img src="https://mintlify.s3-us-west-1.amazonaws.com/pylon/images/linear-2.png" alt=""><figcaption></figcaption></figure>

### Linking Linear Issues <a href="#try-it-out" id="try-it-out"></a>

You can also search for a Linear issue by keywords or identifier, or directly paste in a link to a Linear issue.

### Inside Pylon

Comments in Linear sync as internal notes to Pylon and comments on the Linear internal thread from Pylon sync back to Linear as comments on the ticket.

When a linked Linear issue is completed, the Pylon issue receives a notification. By default, it also moves to **Waiting On You** so you can tell the customer about the completed change.

You can disable that status change in the Linear integration settings by turning off **Automatically move linked Pylon issues to “Waiting On You” when the linked Linear issue is completed or canceled**. You can also control status changes with triggers.

<figure><img src="https://mintlify.s3-us-west-1.amazonaws.com/pylon/images/product-ticketing-linear-done.png" alt=""><figcaption></figcaption></figure>

### Inside Linear

Pylon embeds a native module onto your Linear issue so your product and engineering can also get context on the customer issue.

<figure><img src="https://mintlify.s3-us-west-1.amazonaws.com/pylon/images/product-ticketing-linear-ticket.png" alt=""><figcaption></figcaption></figure>

### Linear Customer Requests

Pylon can also be configured to create Customer Requests in Linear. To set this up, [learn more here](https://support.usepylon.com/articles/1238677178-how-does-the-linear-customer-requests-integration-work).

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2FnDhKhTiAPmOFdbLVVDOG%2FLinear%20Customer%20Requests%20Integration.png?alt=media&amp;token=7f7f7a85-dae2-442e-9cc7-4a81b0dc92b8" alt="" width="563"><figcaption></figcaption></figure>


---

# 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.usepylon.com/pylon-docs/integrations/ticketing/linear.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.