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

# Linear

Turn bug reports, crashes, and APM alerts into Linear issues — forwarded automatically by your rules or manually with a click. Luciq offers a **two-way integration** with Linear: status changes on the Linear issue are reflected on the matching report in your Luciq dashboard, and priority stays in sync both ways.

***

Linear connects to Luciq through a **Shared Credentials** — a set of shared Linear credentials your team authorizes once and reuses. You sign in to Linear through OAuth 2.0; tokens refresh automatically, so there's no manual rotation.

{% hint style="info" %}
Each Linear workspace connects to Luciq through a single connection. Authorize a workspace once, then reuse that connection across all your apps.
{% endhint %}

## Connect Linear

Linear connections are created and managed on the **Shared credentials** (Connections) page in your account settings, then selected when you set up the integration.

{% stepper %}
{% step %}
**Create a Linear connection**

Open the **Shared credentials** page, start a new connection, choose **Linear**, and select **OAuth 2.0**.

{% hint style="warning" %}
Creating or managing a connection requires the **Connections** permission (under Account Management), typically available to admins and owners. If you don't have it, ask an admin to authorize the workspace once — after that, you can select the existing connection yourself when setting up the integration.
{% endhint %}
{% endstep %}

{% step %}
**Authorize your Linear workspace**

You'll be redirected to Linear to sign in and approve the requested permissions. Luciq connects to the workspace you authorize — there's no separate workspace-picker step.
{% endstep %}
{% endstepper %}

## Set up, test, and finish

{% stepper %}
{% step %}
**Add the integration and pick your connection**

Go to **Settings → Integrations → Linear** and select your Linear connection from the list. (If none exist yet and you have permission, you can create one from here.)
{% endstep %}

{% step %}
**Pick a team and configure fields**

Choose the Linear **Team** to forward to — this is the only required field, and selecting it loads the options below. You can then configure, all optional:

* **Status** — defaults to **Triage** when the team has a triage workflow; otherwise left unset.
* **Priority** and **Assignee**.
* **Labels** — add one or more.
* **Estimate** — available when the team uses estimation; the options follow the team's estimation scale.
* **Cycle** — choose a specific cycle, or **Current** / **Upcoming**. The Current and Upcoming options always resolve to the team's live cycle at the moment each issue is forwarded, so issues land in the right rolling cycle.

You can also choose which information from your Luciq report is forwarded to Linear.
{% endstep %}

{% step %}
**Test the integration**

Click **Test** to confirm Luciq can create an issue in your target team.
{% endstep %}

{% step %}
**Finish setup and enable two-way sync**

All done! From this final page you can enable **two-way integration** and turn on automatic forwarding. These can be reconfigured at any time.
{% endstep %}

{% step %}
**Start receiving issues**

Bug reports, crashes, and APM alerts now arrive as issues in your Linear team — automatically through your rules, or manually with a single click.
{% endstep %}
{% endstepper %}

***

### Two-way sync

On the finish step you can enable syncing between the Linear issue and the linked Luciq report:

* **Status** — with **two-way integration** on, moving the issue between workflow states in Linear updates the matching report's status on your Luciq dashboard.
* **Priority** — turn on **two-way sync for priority** to reflect priority changes in both directions.
* **Comments and tags** — turn on one-way sync to post comments and tags you add in Luciq to the linked Linear issue.

### Priority Mapping

| Luciq Priority | Linear Priority |
| -------------- | --------------- |
| NA             | No priority     |
| Trivial        | Low             |
| Minor          | Medium          |
| Major          | High            |
| Blocker        | Urgent          |

### Privacy

To learn more about our privacy policy, please visit the following link: [Privacy Policy](https://www.luciq.ai/privacy).


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.luciq.ai/product-guides-and-integrations/integrations/linear.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.