Skip to content
IonWarpTry for free
IonWarp Docs

Linear

The PR's ticket, so reviews know what is in scope.

Category: devtools · Auth: OAuth

Website · Provider API docs

Connect Linear once in Settings → Integrations and every project you enable it for can use it.

Quickstart

  1. Connect — open Settings → Integrations in your dashboard and choose Connect with Linear. You approve access on Linear's own consent screen; no key is ever pasted. The granted access is verified with Linear before it is stored.
  2. Enable it for a project — on the Linear card, open Projects and tick each project that should use it; a project you leave unticked does not see the connection. Access stays fresh on its own; if Linear revokes it, the connection shows Reconnect.

How reviews find the pull request's ticket

No special issue naming is needed — the pull request only has to point at the issue. On every review the reviewer asks Linear three ways at once:

  • The issue key in the branch name, PR title or description, in any case: ENG-123, eng-123-fix-login, "Fixes ENG-123". A branch created from the issue usually carries its key already.
  • A branch Linear has linked to the issue.
  • A pull request linked on the issue — by Linear's GitHub integration or a link added by hand — then the key does not have to appear anywhere.

When a pull request names several issues, the review planner picks the one it is for (a line like "ignore ENG-122" is read as meant). The review comment shows it as Scope: ENG-123, and a re-review after a push keeps it. Every reviewer then checks what the ticket asks for, and work the ticket explicitly defers is reported as a follow-up rather than a defect.

A pull request with no linked issue is reviewed exactly as before — a review never guesses a ticket from the title. The ticket is read fresh for every review and kept with that review's record, like the pull request's own description; a long ticket description is cut to fit the review. If Linear does not answer, the review runs without it.

In chat, ask "Which ticket is PR #12 for?". Chat can also search by text, and says when a match comes from a search rather than a link.

What the review writes back

The connection asks Linear for read access plus the right to create issues and their attachments — never full write access. With it, the review keeps one status link on the pull request's ticket — IonWarp review · PR #52 with a line such as 1 should-fix open or Merged · 2 fixed — updated in place after each review and at merge, linking to the review page. Counts and a link only: no finding text, no status changes. A Linear connection made before this keeps reading and shows Reconnect; consenting again turns the status link on.

On the review page, Track in Linear on an open finding files it as an issue in the ticket's team, mentioning the ticket and linking the pull request — only when someone clicks it, and once per finding (the row then names the issue).

Actions

ActionDescriptionTypeRuns
linear.attachment.upsertAttach a link with a title and status line to one Linear issue. The same URL on the same issue updates that attachment in place — never a second one.WriteAutomatic
linear.issue.createCreate one Linear issue in the team of an existing issue, mentioning it, for work a review found (e.g. a finding the team tracks instead of fixing now).WriteAutomatic

Learn more

On this page

IonWarp logoIonWarp

Ready to build? Connect an agent and go — no credit card needed to start.

Get startedSee our plans