Where do I see progress on small features when the tickets live in a Linear project?
Tares shows progress on the project page, which lists each ticket with the builder that held it, its pull request and its review rounds. Your tickets stay in Linear, the crew’s sessions update them there with their own tools, and Tares reads the ticket’s title, status and order about once a minute. Open the project’s page for the full record and its Tickets page for the Linear sync.
How it works
Linear stays the home of the ticket. Two things feed the project page, and they come from different places.
- From Linear. Tares only reads from Linear. Sessions create and change tickets in Linear itself. Tares picks up each ticket’s title, status, order and identifier such as
ENG-123, about once a minute. It also reads the Linear project’s milestones and which tickets belong to each, and it turns an issue that blocks another into a dependency. - From the crew’s work. The project page adds the builder that held the ticket, its pull request and its review rounds.
Linear workflow states map to Tares statuses like this:
| Linear state | Tares status |
|---|---|
| backlog, unstarted, triage | todo |
| started | in_progress |
| completed | done |
| canceled, duplicate | canceled |
Every change in Linear also becomes an event on the linear source, so triggers and agents can react to it. The event types are ticket_created, ticket_renamed, ticket_status, ticket_reordered and ticket_removed. An issue that leaves the Linear project becomes canceled in Tares instead of disappearing, so its working doc stays reachable.
Set it up
- Connect Linear in Settings > Linear. On Tares Cloud, click Connect Linear and approve the Tares app. On your own Tares, paste a personal API key, where read access is enough.
- Link the project. On the project’s Tickets page, click Use a Linear project and pick one. A project that already has tickets of its own cannot be linked.
- Confirm the link. The Tickets page shows “Tickets live in Linear project …” and when it last synced. Change an issue in Linear and the ticket follows within a minute. Sync now reads at once.
- Plan the small feature and bring up the crew. The steps are in Get started. The two commands that matter here are:
tares factory crew up
tares factory spec "what you want to build"- Open the project page from the console. Across the top you see four steps, Spec, Build, Review and Done, and a progress bar with one segment per ticket. Open the Tickets fold for the detail.
The connector page, Linear, has the full sync rules and what to do when a sync fails.
What you get
Each small feature stays one ticket in your tracker, and you follow it in two places without copying anything by hand.
- The progress bar. One segment per ticket, so a feature split into a handful of small tickets shows how many are done.
- A state on every ticket. To do, in progress, in review, merged or blocked. A blocked ticket names the tickets it waits for.
- The ticket in progress at the top. You see its milestone, the start of its working doc and the station that holds it.
- Pull request and review rounds. The Tickets fold shows each ticket’s pull request and how many review rounds it took. A ticket that passes on the first round shows one. A ticket where the reviewer asked for changes shows a second round.
- A notice when a station needs you. If the station holding the ticket asked for a permission, a prompt or an answer, a notice says it is waiting for you and shows its last message. The project page also lists questions under questions waiting for you.
- Decisions and assumptions. The answers you gave and the choices the crew made on its own sit in their own folds.
The end-to-end walkthrough shows these folds on a real project, finished and mid-build.
When something else fits
- If you want Tares to hold the tickets itself, leave the project unlinked. Tares tickets are the default ticket source, and Stop using Linear on the Tickets page keeps the tickets you have as Tares tickets.
- If your tickets live in a GitHub repo, link the repo as GitHub Issues. Tares reads those the same way, and sessions update them with their own tools.
- If you want to change a Linear ticket from Tares, do it through a session, because Tares reads Linear and does not write to it.