The verdict
Linear is built like a piece of hardware: keyboard-first, instant, and stubborn about how work should move. Teams that accept its cycle model get the least friction we have tested in a tracker; teams that want their own process imposed on it will fight it every day.
First contact
Linear loads in about a second and never asks you to wait again. The first ten minutes are spent discovering that C creates an issue, that every field can be reached without a mouse, and that the command palette is not a gimmick but the actual way the app is meant to be driven. Our team imported four hundred issues from a spreadsheet and had them triaged before the coffee cooled. The opinion shows up immediately: issues belong to cycles, cycles belong to projects, and projects belong to a roadmap. There is no blank canvas to design. If your team already runs in sprints this feels like recognition; if it runs in a continuous flow, the app will spend the first week telling you so.
In use
After a week nobody was talking about the tool, which is the highest compliment available to an issue tracker. Updates propagate to every open client instantly, so two people editing the same issue do not overwrite each other or refresh to find out. The Git integration is the best we have used: a branch with the issue key in its name moves the ticket on merge without anyone configuring a webhook, and the states it moves between are the ones you would have picked. Cycles force a cadence that our test team resisted for two sprints and then adopted, largely because the burn-down chart made an overloaded week obvious while there was still time to cut scope. Roadmap views are read-only for most people, which we came to see as a feature rather than a limitation.
What it gets wrong
The model is the product and the product is the model, so anything outside it is a workaround. Custom fields exist but are second-class: they filter, they do not drive anything. Reporting past cycle-level charts means exporting, and the export is flat enough that you will rebuild it in a spreadsheet anyway. Private teams, which most companies with clients or contractors eventually need, sit behind the Business tier at nearly double the price, and that jump is the only place Linear feels like it is charging for a fence rather than a feature. Search is fast but literal, with no fuzzy matching across issue descriptions, so finding a ticket you half remember depends on remembering the right words. None of these are defects in the engine. They are edges of a deliberate design.
The verdict
Linear is the tracker we would install at a small product team tomorrow, and the one we would hesitate to hand to an operations department running approvals and non-engineering work. At $8 per user monthly it costs less than the meeting it makes unnecessary, and it wins on the axis most trackers lose: the time between deciding something and recording it. Its 9.1 comes from speed, restraint and a Git integration that actually works, minus a reporting layer that assumes you keep your numbers somewhere else. Teams leaving a bloated tracker will find the transition shorter than expected. Teams needing a flexible workflow engine should look elsewhere, and honestly should not be shopping for a tracker at all.
