Where do I see progress on framework migrations when the tickets live in a Linear project?

Tares shows the progress of a framework migration on the project page, in the Tickets fold, while the tickets themselves stay in your Linear project. Each ticket appears with the builder that held it, its pull request and its review rounds. Sessions update Linear with their own tools, and Tares only reads Linear, so the page follows within about a minute.

How it works

A project can keep its tickets in a Linear project instead of in Tares. Once you link one, the Linear issues become the project’s tickets. This holds for a migration split into many small tickets, such as one per package or per module.

• Linear stays the place where tickets change. Sessions create and change tickets in Linear with their own tools. Tares never writes to Linear.
• Tares reads on a schedule. It syncs title, status, order and identifier about once a minute, plus the milestones of the Linear project and which tickets belong to each.
• Status is mapped for you. Backlog, unstarted and triage show as todo. Started shows as in_progress. Completed shows as done. Canceled and duplicate show as canceled.
• Blocking carries over. If one Linear issue blocks another, the blocked ticket depends on it in Tares, which fits migrations where one step has to land first.
• Removed issues stay visible. An issue that is moved, deleted or archived out of the Linear project becomes canceled in Tares, so its working doc stays reachable.

Every change in Linear also becomes an event on the linear source, keyed by the issue identifier such as ENG-123. The event types are ticket_created, ticket_renamed, ticket_status, ticket_reordered and ticket_removed. Triggers and agents can react to them like any other event.

The software factory for Claude Code adds the build side. Each project you hand to the crew gets a page that records the whole build, and its Tickets fold lists each ticket with the builder that held it, its pull request and its review rounds. A project, end to end walks through one real project on that page.

Set it up

1. If you have not set up the software factory for Claude Code yet, follow Get started first. It covers the sign-ins, the CLI and bringing up the crew.
2. 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.
3. Open the project’s Tickets page and click Use a Linear project. Pick the one that holds your migration tickets. Tares creates the linear source the first time you link a project. A project that already has tickets of its own cannot be linked.
4. Bring up the crew if it is not running, then plan the work:

tares factory crew up
tares factory spec "what you want to build"

5. Open the project page. The Tickets fold shows your Linear tickets, and the progress bar at the top has one segment per ticket.
6. To check the link, look at the Tickets page. It says “Tickets live in Linear project …” and when it last synced. Change an issue in Linear and the ticket follows within a minute. Click Sync now to read at once. The source’s Recent events lists the change.

What you get

• One view of the migration. The four steps across the top of the project page are Spec, Build, Review and Done, with a progress bar that has one segment per ticket.
• Per-ticket state. Each ticket shows as to do, in progress, in review, merged or blocked. A blocked ticket names the tickets it waits for.
• The pull request and review history. Next to each ticket you see its pull request and how many review rounds it took. In the example project, most tickets passed on the first round and two needed a second.
• Milestones. The Linear project’s milestones appear with their tickets, so you can see how far each stage of the migration has come.
• Your tracker stays the source of truth. You keep triaging, renaming and reordering in Linear. If a sync fails, for example after a revoked key, the Tickets page says why and the tickets stay as they were. Connect again in Settings > Linear to resume.
• An exit. Stop using Linear on the Tickets page keeps the tickets as Tares tickets.

When something else fits

• If you want Tares to hold the tickets itself, skip the Linear link and use Tares tickets, as in Get started. Linear then plays no part.
• If the project already has Tares tickets, you cannot link a Linear project to it. Start a new project for the migration instead.
• If you want to change tickets from Tares, do it in Linear. Tares only reads, so edits and new tickets come from sessions or from you in Linear. The Linear connector page has the full details.

Related