Track vs Linear
Track is the zerosoft app that replaces Linear. By our count it covers 95% of the 65 Linear capabilities we measure: 60 included, 4 partial and 1 missing. The table comes from the same data as the product page and was last checked against the code on November 17, 2026.
At a glance
- Parity with Linear
- 95%
- Linear at list price
- $8 / user / month
- Track
- $0 on your server (AGPLv3). On zerosoft Cloud: free plan, then usage. Seats are not billed.
- License of Track
- AGPLv3, source on GitHub
- Last reviewed
- November 17, 2026
Linear Standard costs $8 per user per month. A team of 10 pays $960 a year. Track on your server costs $0.
Capability by capability. Our count, from the code.
parity with Linear
95%of what Linear does, by our count
- Included
- 60
- Partial
- 4
- Missing
- 1
We measured 65 Linear capabilities: each one we have scores 1, a partial one 0.5 and a missing one 0, with double weight for the core ones; this is our own assessment, checked against the code on November 17, 2026. See the changelog
- Issues and data model100%
- Views and navigation100%
- Collaboration and notifications100%
- Planning100%
- Automation100%
- Integrations and API91%
- Admin and permissions62%
- Analytics100%
- Mobile and offline50%
- AI100%
- Import and export100%
- Keyboard and UX100%
Everything Track includes67
[x] Included[+] Better[~] Partial
| Capability | Track | Linear |
|---|---|---|
| Issues and data model | ||
| Status, priority, assignee, labels, estimate, start and due dates | IncludedUrgent, high, medium, low and No priority, set with P and 0 to 4, as in Linear | Linear: Yes |
| Sub-issues and relations (blocks, related, duplicate) | IncludedSub-issues section with progress, inline creation (Enter for the next, paste a list), edit in place, drag to reorder, add existing, set or remove parent (⌘⇧P); lists show them under the parent or hide them | Linear: Yes |
| Rich descriptions and comments | IncludedVisual editor (WYSIWYG) for descriptions, comments and quick create: markdown shortcuts as you type (# headings, - and 1. lists, [] checklists, > quotes, ``` code, **bold**, `code`), / to insert blocks, @ people and issues, # issue mentions with their status, checklists ticked with a click or ⌘↵, pasted or dropped images and a toolbar on selection. Saved as the same markdown the API and emails read | Linear: Yes |
| Attachments on issues | IncludedAny file type and size, private, with image and PDF preview | Linear: Yes |
| Issue templates | IncludedPer project, with one default template that quick create fills in | Linear: Yes |
| Project templates | IncludedSave a project as a template (description, priority, teams, labels, milestones with their offset from the start date, open issues with milestone, parent and labels) and pick it when creating a project; rename and delete in settings. Issues from private teams stay out unless you can see them. No editing the template contents in place yet | Linear: Yes |
| Recurring issues | IncludedDaily, weekly, monthly or yearly, with a repeat interval | Linear: Yes |
| Editable workflow statuses | IncludedPer team, grouped in categories (backlog, todo, started, done, cancelled) | Linear: Yes |
| Issue activity history | IncludedTimeline of changes next to the comments | Linear: Yes |
| Delete issue and copy link from its page | IncludedMenu and shortcuts: delete with confirmation (⌘⌫), copy link (⌘⇧,) | Linear: Yes |
| Projects with lead, target date, health and updates | IncludedProjects as in Linear: lead, members, several teams, six statuses, start and target dates, description with the issue editor, resources (links), milestones with their progress, a scope versus completed chart and progress by issues or estimate; one properties row under the title and a summary column; the Issues tab is the same list as a team (list or board, filters, grouping by milestone, + per group, drag and drop). Set from the issue or the peek with ⇧P. Track uses Linear names: teams hold the key, statuses and cycles | Linear: Yes |
| Initiatives and sub-initiatives | IncludedOwner, status, target date, projects and sub-initiatives, combined progress; initiative updates with health and text that notify the owner and project leads, and the latest one sets the health (without updates, the worst of its active projects). No comments or reminders on initiative updates yet | Linear: Yes |
| Customer requests linked to issues | IncludedFrom the issue (CRM company, contact or a name or email matched by domain), from the CRM record and through POST /api/v1/track/requests for email, forms or Flow; importance and quote; Track › Customers and sort by customer count or won-deal revenue. Chat and Lines have no button yet: they go through the API or Flow | Linear: Yes |
| Views and navigation | ||
| List and board views | IncludedBoard with drag between columns; in the list, drag rows onto another group (status, priority, assignee, cycle, team, project milestone) or onto a project in the sidebar | Linear: Yes |
| Timeline (Gantt) view | IncludedDragging bars changes start and due dates | Linear: Yes |
| Calendar view of issues | BetterIssues placed by due date | Linear: No |
| Grouping and sorting | IncludedGroup by status, assignee, priority, cycle, label, team, project or project milestone; order by manual (drag rows), priority, updated, created, due date or estimate; sub-grouping inside each group | Linear: Yes |
| Issue filters | IncludedF opens the filter menu: any property (status, priority, assignee, creator, labels, cycle, milestone, estimate, dates, relations, sub-issues) with is, is not, empty or before/after, matching all or any. Quick filter by typing a value; filters live in the URL | Linear: Yes |
| Saved views | IncludedPersonal and team views per team, and workspace views on Issues and a project's Issues tab that everyone in the workspace sees (only the owner edits them); filters, grouping, sort, sub-issues and list/board; favorites in the sidebar, save changes, link to share. No view alerts to Slack yet | Linear: Yes |
| Issues across all teams and My issues | IncludedSame list as a team: filters (also by team and project), list or board, grouping by status, assignee, priority, project, team, cycle or label, sub-grouping, ordering incl. manual and estimate, completed issues (all, past week, none), empty groups and visible properties, remembered per view and person; saved views, personal or shared with the workspace | Linear: Yes |
| Find issues from Cmd+K | IncludedBy title or identifier, from any app | Linear: Yes |
| Roadmap across projects | IncludedTimeline of projects or initiatives by weeks, months or quarters; drag bars and edges (or arrow keys) to change dates, milestones, today line, group by initiative, status or lead | Linear: Yes |
| Collaboration and notifications | ||
| Comments with @mentions, edit and delete | Included | Linear: Yes |
| Subscribe to an issue | Included | Linear: Yes |
| Inbox with filters, snooze and reminders | Included | Linear: Yes |
| Email notifications, immediate or daily digest | Included | Linear: Yes |
| Live updates in lists, board and issue | IncludedList, board and issue page refresh on their own every 4 seconds while the tab is visible (polling, no websockets), and the issue shows who else has it open | Linear: Yes |
| Comment reactions and threads | IncludedEmoji reactions, one-level reply threads, resolve and reopen, link to a comment | Linear: Yes |
| Project updates with health and reminders | IncludedOn track, at risk or off track with text, progress delta, comments, emoji reactions on updates and comments, history of date and lead changes, Update missing state; weekly or biweekly reminder to the lead in the Inbox; members and followers notified. No Slack posting | Linear: Yes |
| Planning | ||
| Cycles with automatic cadence and rollover | Included | Linear: Yes |
| Milestones with date and progress | Included | Linear: Yes |
| Triage: accept, decline, mark duplicate | IncludedReceives issues from the API, Chat, Flow, GitHub and Agents | Linear: Yes |
| Triage rules and rotating triage owner | IncludedRules run top to bottom when an issue enters triage and set priority, assignee, labels, cycle, accept it into a status or move it to another team's triage queue (where that team's rules run); a daily or weekly rotation notifies or assigns the person on duty. No PagerDuty or Opsgenie schedules | Linear: Yes |
| SLAs by priority | IncludedPer team and priority (urgent 24 h and high 1 week by default), countdown in the issue, lists and triage, at risk and breached notices to subscribers; calendar hours, no business days | Linear: Yes |
| Cycle velocity, capacity and scope creep | IncludedBurn-up of scope, started and completed per day, scope added and removed, rolled over, velocity of the last 3 cycles and capacity; ended cycles close on their own and roll over. Rebuilt from the activity log, not frozen at close | Linear: Yes |
| Automation | ||
| Automations triggered by issue events | BetterFlow runs on issue created, updated or status changed and can create or update issues | Linear: Yes |
| Status changes from GitHub pull requests | IncludedPR opened moves to in progress, merge moves to done | Linear: Yes |
| Copy git branch name from an issue | Included | Linear: Yes |
| Auto-close and auto-archive of stale issues | IncludedPer team, 1 to 12 months, daily from the cron; new teams archive closed issues after 6 months like Linear. Skips current cycles and active projects; archive by hand from ⌘K, and an archived issue shows a banner with Restore | Linear: Yes |
| Agents that work on issues | IncludedDelegate an issue to an agent from the Agents app or to an external agent: a session in the issue shows its thoughts, actions, questions and answers, and it can move the issue. External agents get a signed webhook and answer with their token through /api/v1/track/agent-sessions | Linear: Yes |
| Integrations and API | ||
| Public API and webhooks for issues | IncludedREST API for issues, comments, teams, cycles, statuses, labels and people with scoped keys; signed webhooks for issue, comment and team events with retries and a delivery log | Linear: Yes |
| GitHub integration | IncludedGitHub App or webhook: links by ID and magic words, status per team for draft, open, review and merge, checks and reviews on the issue, GitHub Issues sync from GitHub; no GitLab | Linear: Yes |
| Slack: issues from messages and channel notifications | IncludedIssues from a message (with synced thread) and from /track, channel notifications per team and issue link previews; no personal DMs or Asks | Linear: Yes |
| Intercom, Zendesk, Sentry and Figma integrations | PartialSentry creates issues and is resolved on completion, Figma links show a live preview, Zendesk and Intercom tickets get a note on close and can create issues by API; no app inside the Zendesk or Intercom sidebar | Linear: Yes |
| Issues created from zerosoft Chat, Flow and Agents | BetterIncluded, they land in triage | Linear: No |
| Admin and permissions | ||
| Workspace members | Included | Linear: Yes |
| Private teams, guests and per-team roles | PartialPrivate teams for their members and guests limited to chosen teams, also in the API, search and integrations; no owner role per team, workspace admins manage access | Linear: Yes |
| SSO, SAML, SCIM and audit log | PartialTrack audit log with actor, before and after, source and IP, filters and CSV export; sign-in is Google only, no SAML or SCIM | Linear: Yes |
| Analytics | ||
| Team overview | IncludedCurrent cycle, overdue, triage and open issues | Linear: Yes |
| Insights: cycle time, lead time, burn-up, CSV | IncludedCount, effort, cycle time, lead time and issue age; slice and segment by status, assignee, label, priority, project, team, cycle or week; burn-up; drill into issues; CSV and shareable link. Time measures are bars of the median, not scatterplots; no triage time | Linear: Yes |
| Dashboards | IncludedSaved insights as chart, table or number, wide or narrow, reordered; dashboard filters on top of each widget; workspace or personal | Linear: Yes |
| Mobile and offline | ||
| Mobile web at 390 px | IncludedList, issue and board work without horizontal page scroll | Linear: Yes |
| Offline mode | PartialLists, issues and projects already opened on the device are readable offline; status, priority, assignee, dates, title, description, new issues and comments are saved on the device and sent when back online, with an "edited elsewhere" notice. No full local copy of the workspace like Linear, and attachments and AI need a connection | Linear: Yes |
| AI | ||
| AI triage suggestions: labels, assignee, duplicates | IncludedAssignee, labels, priority and possible duplicates with a reason, accepted or dismissed in one click; per team each kind can be suggested, applied automatically or turned off. Needs an AI Gateway key | Linear: Yes |
| AI thread summaries and issues from free text | IncludedSummary of the issue and its discussion, a team update draft from the last 14 days, and an issue drafted from pasted text (title, description, priority, labels). Needs an AI Gateway key | Linear: Yes |
| Assistant that answers and makes changes | IncludedSide panel with ⌘J on every page and a full-page chat with history: lists teams and projects with their health, creates issues and sets a project's update reminder. Every change waits for a Confirm click. Needs an OpenRouter key | Linear: Yes |
| MCP server for external agents | IncludedStreamable HTTP with an API key: search, read, create and update issues, comment, and list teams, cycles, labels and people; read-only URL | Linear: Yes |
| Import and export | ||
| Importers from Linear, Jira, GitHub Issues and Asana | IncludedLinear by API brings the whole workspace: teams with their workflow, projects with milestones and updates, cycles, issues with their original IDs, comment threads, links and pull requests, relations, sub-issues and dates; people matched by email, with invites for the missing. Re-running updates what changed and never duplicates. Also Linear CSV, Jira Cloud (API or CSV), GitHub Issues, Asana and Shortcut. Not imported: Linear documents, initiatives, custom views and file uploads (they stay as links) | Linear: Yes |
| Two-way sync with Linear during the move | PartialTrack › Settings › Integrations › Linear: connect with Login with Linear or a personal API key, pick teams and direction (two-way or one way), a full import with progress, then live changes both ways: Linear webhooks plus a check every 5 minutes, and Track changes sent through a queue with retries. Title, description, status, priority, estimate, assignee, labels, due date, parent, project and milestone go both ways; cycles, comments and links come in; comments go out. The latest change wins per field. Deletions are not copied, and it has only been tested against a simulated Linear so far | Linear: No |
| CSV import and export | IncludedCSV import with column mapping and CSV export of issues | Linear: Yes |
| Keyboard and UX | ||
| Quick create with C, Create more and inline syntax | IncludedPrefills team and status; !high and @tomorrow in the title | Linear: Yes |
| List navigation with J/K, X, Enter, Esc and / | Included | Linear: Yes |
| Property shortcuts (S, P, A, L) and G to navigate | IncludedS, P, A, I, L, ⇧E, ⇧D, ⇧C, ⇧1-4, ⌘⇧P parent, ⌘⇧O sub-issue, ⌘. and ⌘⇧. copy, X and Shift+click to select, J/K, Enter, F, ⌘B, and G then I, M, E, P, S to navigate. They act on the selection, the hovered row or the open issue | Linear: Yes |
| Actions in Cmd+K | IncludedOn the open issue, hovered row or selection: change status, priority, assignee, labels, estimate, due date, cycle, milestone, set or remove parent, create sub-issue, copy ID, URL and branch, open and delete | Linear: Yes |
| Undo | Included⌘Z and an Undo toast for property changes, bulk edits, reordering, moves between teams and deletes (a deleted issue comes back within 8 seconds), and ⌘⇧Z to redo | Linear: Yes |
| Empty, loading and error states | Included | Linear: Yes |
| Light and dark themes | Included | Linear: Yes |
Where we go further
- Calendar view of issuesIssues placed by due date
- Automations triggered by issue eventsFlow runs on issue created, updated or status changed and can create or update issues
- Issues created from zerosoft Chat, Flow and AgentsIncluded, they land in triage
Still missing (1)
Linear has these and we don't yet. If you need one, vote for it on the public board.
- Native iOS and Android apps with pushVote on the board
Questions.
Can I import from Linear?
Yes. Paste a Linear API key, or upload a CSV export from Linear or Jira, or connect a GitHub repository. You see a preview first; projects, statuses, cycles, milestones, labels and comments come along, and importing again does not duplicate issues.
How is work organized?
By team, like in Linear. Each team has its own identifier, statuses, members, cycles and saved views, and projects group issues from one or more teams behind one outcome. Issues have a priority, estimate, assignee, dates, sub-issues and relations.
Where do I see my work?
In My issues and in the inbox, which collects mentions, assignments and changes to your issues.
Does it have an API or webhooks?
Yes. REST API v1 covers issues, comments, teams, cycles, statuses, labels and people, with scoped keys. Webhooks for issues, comments and teams arrive signed, with retries and a delivery log. There is also an MCP server.
How do I self-host it?
It ships in the same container as the rest of the suite. Issues live in your SQLite file and attachments in the uploads volume.
Guides and posts
- What to do with a feature request that arrives in chatA 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 howHow 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 ruleHow 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 finishRules 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.