Posts about track
What to do with a feature request that arrives in chat
A four-step method for answering feature requests without overpromising: tag in Chat, link to a Track issue, count distinct customers, and tell them when it ships.
Migrate from Linear to Track: what imports and how
How to move your Linear issues to Track with an API key or a CSV export: what comes across (teams, cycles, labels, comments), what stays behind, what to check.
Zero bugs on a small team: triage, deadlines and one rule
How to run a zero-bug policy with three to ten people: a rule with two exits, deadlines by priority, a weekly on-call rotation and Track's triage queue for whatever arrives through Chat or Flow.
How to write an issue someone can actually finish
Rules for issue titles, descriptions and size, three plain-text templates for bugs, tasks and investigations, and how to use sub-issues, relations and estimates in Track.
Track vs Linear: what each does today
Where Linear is ahead, where Track holds up, and who shouldn't switch. Written by the people who build Track, gaps included.
Running two-week cycles in Track: a playbook for small teams
How a small team runs cycles in Track with issues, sub-issues, relations, estimates, custom statuses and four views, plus what it still lacks.
What's inside a $30-per-user project tool
A project tool is a database, a drag-and-drop interface and a login. We list each part, what it costs to run, and where the rest of the price comes from.
What we took from Linear for Track, and what Linear's per-seat price adds up to
Linear is a great issue tracker: fast, keyboard-driven, built around cycles. Its price grows with every hire. Why we built Track, and what it does and doesn't do yet.