Linear: linear
Poll source for Linear. A project can keep its tickets in a Linear project instead of Tares: the
issues become the project’s tickets, and every change made in Linear becomes an event on the
linear source, keyed by the issue’s identifier (ENG-123). Triggers and agents can react to
them like any other event.
Tares only reads from Linear. Sessions create and change tickets in Linear itself.
Set up
- Connect Linear in Settings > Linear. One connection serves the whole workspace.
- On Tares Cloud, click Connect Linear and approve the Tares app in Linear.
- On your own Tares, paste a personal API key (in Linear: Settings, Security and access, Personal API keys). Read access is enough.
- Link a project. On the project’s Tickets page, click Use a Linear project and
pick one. Its issues become the project’s tickets, and Tares creates the
linearsource the first time a project is linked.
A project that already has tickets of its own cannot be linked.
What Tares keeps in sync
- Tickets: title, status, order and identifier, about once a minute. Sync now on the Tickets page reads at once.
- Status, from the issue’s workflow state: backlog, unstarted and triage are
todo, started isin_progress, completed isdone, canceled and duplicate arecanceled. - Milestones: the Linear project’s milestones and which tickets belong to each.
- Dependencies: an issue that blocks another makes the blocked ticket depend on it.
- An issue that leaves the Linear project (moved, deleted or archived) becomes
canceledin Tares rather than disappearing, so its working doc stays reachable.
Events
One event per change, with event_type:
| event_type | when |
|---|---|
ticket_created | an issue was added to the Linear project |
ticket_renamed | its title changed |
ticket_status | it moved to a status that maps to a different Tares status |
ticket_reordered | its order changed |
ticket_removed | it left the Linear project |
The payload carries change, ticket, project, linear_project, the Linear issue, and
from and to for a change of value.
Provided labels
ticket (the key; the issue identifier), project (the Tares project), linear_project.
Verify
The Tickets page shows “Tickets live in Linear project …” and when it last synced. Change an issue in Linear: within a minute the ticket follows, and the source’s Recent events shows the change.
When a sync fails (a revoked key, a Linear project the connection can no longer see), the Tickets page says why and the tickets stay as they were. Connect again in Settings > Linear. To stop, Stop using Linear on the Tickets page keeps the tickets as Tares tickets.