Skip to Content
Tares

Where do I see progress on bug fixes when the tickets live in a Linear project?

Tares shows progress on your bug fixes on the project page, where each Linear ticket appears with its pull request and its review rounds. The ticket stays in Linear, and sessions update it with their own tools. Tares only reads it, about once a minute, and the Crew page and the standup report show the same progress from other angles.

How it works

When you link a Linear project to a Tares project, its issues become the project’s tickets. Tares only reads from Linear. Sessions create and change tickets in Linear itself, so the ticket in your tracker is always the one the crew works on.

Tares syncs the title, status, order and identifier about once a minute. The Linear workflow state maps to a Tares status: backlog, unstarted and triage are todo, started is in_progress, completed is done, and canceled and duplicate are canceled. Every change becomes an event on the linear source, keyed by the issue identifier such as ENG-123. The events are ticket_created, ticket_renamed, ticket_status, ticket_reordered and ticket_removed.

The project page for the build then shows where each bug fix stands:

  • Across the top, four steps (Spec, Build, Review and Done) and a progress bar with one segment per ticket.
  • The Tickets fold lists each ticket with the builder that held it, its pull request and its review rounds. Each ticket shows its state: to do, in progress, in review, merged or blocked. A blocked ticket names the tickets it waits for.
  • The GitHub fold lists the repos the project changes, with their open and merged pull requests.
  • The Decisions and Assumptions folds hold the questions the crew asked you and the choices it made on its own.

For a closer look, the Crew page at http://127.0.0.1:8787/crew on a local Tares shows each station, the tickets it holds with their stage and pull request, and its last lines. For how a whole build reads on these pages, see A project, end to end.

Set it up

  1. 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 from Linear (Settings, Security and access, Personal API keys). Read access is enough.
  2. Open 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. Tares creates the linear source the first time you link a project. The connector details are on the Linear connector page.
  3. Give Tares access to GitHub, in Settings > GitHub for a local Tares or Connect GitHub on Tares Cloud, so it can show pull requests.
  4. Bring up the crew. On a local Tares, start Tares, then start the MCP endpoint in a second terminal, then bring up the crew and plan the project. On Tares Cloud, run tares login instead and skip the MCP step. The full order is in Get started.
tares up
tares mcp --transport streamable-http
tares factory crew up
tares factory spec "what you want to build"
  1. Open the project page and unfold Tickets to follow each bug fix. Click Sync now on the Tickets page to read from Linear at once.
  2. To check the link, look at the Tickets page. It says “Tickets live in Linear project …” and shows when it last synced. Change an issue in Linear and the ticket follows within a minute. The source’s Recent events shows the change.

What you get

  • One place to see each bug fix: the ticket, the builder that held it, its pull request and every review round, on the project page.
  • A progress bar with one segment per ticket, so you see how many fixes are done at a glance.
  • Linear stays the source of truth. You and the sessions keep updating tickets there, and Tares follows within about a minute.
  • Milestones and dependencies carry over. The Linear project’s milestones and which tickets belong to each are kept in sync, and an issue that blocks another makes the blocked ticket depend on it.
  • Tickets that leave the Linear project (moved, deleted or archived) become canceled in Tares instead of disappearing, so their working docs stay reachable.
  • A Standup report, top right on the Crew page, that lists what is done, started, in review, blocked and waiting on you across the projects handed to the crew, with pull request links. Copy takes the markdown and Send to Slack posts it to a channel you pick.
  • Triggers and agents can react to the linear events like any other event.

When something else fits

  • If a sync fails, for example after a revoked key or 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.
  • If you want Tares to hold the tickets itself, use Stop using Linear on the Tickets page. It keeps the tickets as Tares tickets.
  • If your tickets are GitHub Issues, link the repo to the project instead. Tares reads those the same way.

Still stuck? Get help

Last updated on
Quickstart