What we build next.
Suggest ideas, vote for the ones you need and follow their status. The most voted move up the list.
Track: Create issues from email with a per-project intake address
Linear gives each team a unique intake email; new emails become issues in triage with sender and attachments, and replies do not create new issues (https://linear.app/integrations/create-issues-via-email, https://linear.app/docs/customer-requests). Track already has a triage queue for non-app sources (lib/track-bulk.ts, source column) but no email entry point. Customers and non-users report bugs by email, so this turns Track into a lightweight help desk for small teams. First scope: a per-project address using the existing inbound email handling, issues created with source email and triage on, sender stored on the issue, attachments copied. Priority: low. Effort: M. Compared with Linear.
- 1
Track: Share saved views with the team and allow workspace-level views
Linear views can be personal or shared with a team or the workspace, and filtered views can be shared by URL or shortcut (https://linear.app/changelog, Jul 2, 2026 entry). Track saved views are filtered by user_id in listIssueViews (lib/track-data.ts), so each teammate has to rebuild the same Bugs this week view, and views only exist inside one project. First scope: a visibility flag (personal or team) on track_issue_views, shared views listed for all project members, and saved views on the cross-project Issues page. Priority: medium. Effort: S. Compared with Linear.
- 0
Track: Preload a default issue template per project in quick create
Linear lets a team mark a template as the default so every new issue starts from it (https://linear.app/docs/issue-templates). Track had templates per project (lib/track-templates.ts) that had to be picked by hand each time. A small team that files most issues in one shape, such as bug reports, repeats that pick on every issue. Built: a Default checkbox on the template form, one default per project, and quick create fills it in on an empty draft.
Track: Send a saved view digest to Slack or email
Linear lets people subscribe to a view and get a notification when issues enter it, including to a Slack channel (https://linear.app/docs/custom-views). Track saved views are shared with the team (components/track/SavedViewsMenu.tsx) but nobody is told when something new matches. A weekly bug triage or a Fridays-due view only works if someone remembers to open it. First scope: a Notify me toggle per view that adds a daily email or Slack summary of newly matching issues, claimed per row by the existing cron.
- 0
Track: Create projects from a project template
Linear lets a workspace save project templates with a description, milestones and a set of issues, then start new projects from them (https://linear.app/docs/project-templates). Track has issue templates per project (lib/track-templates.ts) but every new project starts empty. Teams that run the same kind of project, such as a launch or a client onboarding, rebuild its milestones and first issues each time. First scope: save a project as a template with its milestones and open issues, and a Use template choice in the new project form.
Track: Add sub-teams that roll up under a parent team
Linear supports multi-level sub-teams so teams mirror the org structure, with issues and views rolling up to the parent (https://linear-web.pages.dev/changelog/2026-04-09-multi-level-sub-teams). Track has a flat list of teams that hold the key, statuses and cycles (lib/track-data.ts), with no parent. Teams of 10 to 20 people start splitting into groups such as web and mobile and want one view of both. First scope: an optional parent team, and a team issues view that includes the issues of its children.
Track: Add team documents pinned to each project page
Linear lets a team pin shared documents to a team page, next to its issues (https://linear-web.pages.dev/changelog/2026-06-04-team-documents). Track projects have a description and updates but no place for specs, runbooks or onboarding pages, and the link from Track to Docs is only per issue (app/[locale]/app/track). A small team ends up with a doc per project that nobody finds. First scope: pin Docs pages to a project from its Overview tab, listed with title and last edit, opening in Docs.
Track: Notify and create issues from Microsoft Teams channels
Linear for Microsoft Teams lets people mention @Linear in a channel to create work and get issue notifications (https://linear-web.pages.dev/changelog/2026-04-16-linear-for-microsoft-teams). Track only reaches Teams through Flow, and the Slack integration (lib/track-slack.ts) has no Teams equivalent. Teams are common in small companies that already pay for Microsoft 365. First scope: an incoming webhook per project for activity notices to a Teams channel, then a bot command to create an issue from a message.
Track: Create a Slack channel automatically for each new project
Linear can create and link a Slack channel when a project is created, and posts project updates there (https://linear-web.pages.dev/changelog/2026-05-21-project-slack-channels). Track lets a project post issue activity to a channel chosen by hand in lib/track-slack.ts, but it never creates the channel. A small team loses time setting up one channel per project and wiring the notifications. First scope: a project setting that creates a channel named after the project through the existing Slack connection, links it and posts the project updates there.
- 0
Track: Auto-close stale issues and auto-archive completed ones
Linear lets each team auto-close issues untouched for N months and auto-archive completed issues after a period, which keeps lists short without manual cleanup (https://linear.app/docs). Track keeps every issue in its list forever unless deleted. First scope: per-project settings for auto-close (move to a cancelled status after 1, 3 or 6 months without activity, with a comment explaining why) and auto-archive (hide done/cancelled issues older than N months from default views, still searchable and restorable), run from the hourly cron with compare-and-set claims. Priority: low. Effort: S. Compared with Linear.
- 0
Track: Set SLAs by priority and flag issues about to breach
Linear supports issue SLAs and triage responsibility so urgent bugs get a response time (https://linear.app/pricing, Triage section); Jira Service Management triggers automations on SLA breach. Track has no response or resolution target. First scope: per-project SLA per priority (e.g. urgent 24 h, high 3 days) counted from creation or triage acceptance, a countdown chip on rows and the issue page, an "SLA" filter and sort, a notification to the assignee and project owner at 80 % and at breach, and an issue.sla_breached event for Flow. Priority: medium. Effort: S. Compared with Linear, Jira.
- 0
Track: Link CRM companies and contacts to issues as customer requests
Linear Customer Requests link feedback to issues and projects, show a customer page with every request, and let views sort issues by customer count, tier or revenue (https://linear.app/docs/customer-requests). zerosoft already has the CRM and Chat, so this can work without any third-party sync. First scope: a "Requested by" field on issues that links CRM companies or contacts (and the Chat conversation when created from Chat), a request count and summed deal value column in lists with sort, and a Track section on the CRM company page listing its requested issues and their status. Priority: medium. Effort: M. Compared with Linear.
- 0
Track: Suggest labels, assignee and possible duplicates for issues in triage
Linear Triage Intelligence proposes labels, assignee, project and duplicates for incoming issues (https://linear.app/pricing). Track's triage queue (issues from Chat, Flow, API, GitHub, Agents) is fully manual. First scope, only when AI is enabled for the workspace: on each triage issue, show suggested labels and assignee based on the last 200 accepted issues of the project, and the top 3 similar open issues by title and description with a one-click "Mark duplicate"; accept applies the suggestions in one click. Log which suggestions were accepted. Priority: medium. Effort: M. Compared with Linear.
- 0
Track: Add private projects and guest members limited to the projects they are invited to
Linear Business has private teams and guest accounts (https://linear.app/pricing); GitHub Projects and Jira have per-project permissions. In Track every workspace member sees and edits every project (canAccessTrackProject checks only the workspace), so teams that work with contractors or clients cannot use it. First scope: a project visibility setting (workspace / private with a member list), guest role that only sees projects they are added to and cannot see Cmd+K results or Inbox items from others, and enforcement in every /api/track route plus search and notifications. Priority: medium. Effort: M. Compared with Linear, Jira.
- 0
Track: Show cycle velocity, burn-up and cycle time so teams can plan the next cycle
Linear Insights charts issue count and effort, cycle time, lead time, triage time and issue age, with slicing, segments and a burn-up, and exports to CSV (https://linear.app/docs/insights); cycles show scope and completion over time. Track's overview only shows done/total for the current cycle. First scope: on each cycle, a burn-up of scope vs completed points or issues (from the activity log), velocity of the last 3 completed cycles shown when creating the next one, and a cycle-time / lead-time panel per project with median and p75, using status category changes already logged in track activities. Priority: high. Effort: M. Compared with Linear, Jira.
- 0
Track: Add projects with lead, target date, health and written updates, plus a roadmap across them
In Linear a project has a lead, members, start and target dates, status, and periodic updates marked On track / At risk / Off track with reminders to the lead (https://linear.app/docs/initiative-and-project-updates); initiatives group projects into a roadmap. A Track project is closer to a Linear team: it has milestones but no lead, target date, health or updates, and there is no view across projects. First scope: lead, target date and status on track_projects; a project update composer with health and auto-included progress since the last update; a weekly reminder to the lead; a roadmap page with one bar per project (start to target) and its latest health. Priority: high. Effort: L. Compared with Linear.
- 0
Track: Create issues from Slack messages and post issue activity to a Slack channel
Linear's Slack integration creates an issue from any message (with a synced comment thread), posts team and project activity to a channel, sends personal notifications as DMs and unfurls issue links (https://linear.app/docs/slack). Track only reaches Slack if someone builds a Flow with the generic Slack node. First scope: one-click Slack connect in Track › Settings, a message shortcut "Create Track issue" that opens a modal with project, priority and assignee and links back to the message, per-project channel notifications for created / completed / commented, and unfurls for issue URLs. Priority: high. Effort: M. Compared with Linear.
- 0
Track: Update lists, board and issue pages live when a teammate changes something
Linear syncs every change to every open client instantly. In Track the project list, board and issue page only change on reload: in a browser test, renaming an issue from a second session left the open list showing the old title after 15 seconds and a focus event (components/track/ProjectPageClient.tsx has no polling or subscription). Two people triaging the same board see different states and overwrite each other. First scope: a per-workspace change feed (SSE, or polling every few seconds while the tab is visible) carrying issue id + updated_at, merged into useIssueStore; refetch on window focus; on the issue page, show new comments and a notice when the description changed underneath an open editor. Priority: high. Effort: M. Compared with Linear.
- 0
Track: Import issues from Linear, Jira, GitHub Issues and CSV, and export a project to CSV
Linear has guided importers for Jira, GitHub Issues, Asana, Shortcut and Linear itself that bring issues, projects, labels and users, with user mapping and an undo window (https://linear.app/docs/import-issues). Track has no importer and no export: a team switching over has to retype its backlog, which is the first reason not to switch. First scope: a CSV importer in Track › Settings with column mapping (title, description, status, priority, assignee by email, labels, due date, estimate, parent) into one project, plus a Linear importer using a personal API key (issues, comments, labels, states mapped by category) and a GitHub Issues importer per repo. Export: CSV of the current list view. Priority: high. Effort: M. Compared with Linear, Jira.
- 0
Track: Log activity and emit events when completing a cycle moves issues
completeCycle in lib/track-data.ts moves unfinished issues with a raw UPDATE on track_issues, so no cycle_change activity is written, no issue.updated Flow event fires, and assignees get no notice, unlike updateIssue and bulk edit, which keep activity and notifications (lib/track-bulk.ts). Linear keeps the issue history and the cycle snapshot when rolling over (https://linear.app/docs/use-cycles). The issue timeline then shows a cycle that silently changed. First scope: collect moved issue ids in the transaction, then write cycle_change activities and emit issue.updated for each after commit. Priority: low. Effort: S. Compared with Linear.
- 0
Track: Add milestones with target dates and progress inside a project
Linear projects can be split into milestones with optional target dates, each showing completion percentage from its issues in the overview and timeline (https://linear.app/docs/project-milestones), and projects carry health updates (on track, at risk, off track) (https://linear.app/docs/initiative-and-project-updates). Track has no layer between a project and its issues: track_projects has no target date or lead and there is no milestone table (lib/schema/baseline.ts). Small teams shipping a launch need to see whether phase 1 is done before the deadline. First scope: track_milestones (name, target date, position), a milestone property on issues, progress per milestone on the project page and in the Gantt view. Priority: medium. Effort: M. Compared with Linear.
- 0
Track: Add group by and more sort options to list and board views
Linear display options let you group lists and boards by status, assignee, priority, cycle, label or project and order by priority, due date, updated or manual (https://linear.app/docs/display-options). Track's board only groups by status (components/track/IssuesBoard.tsx), the project list has no grouping, and the saved view sort enum is limited to newest, oldest, priority and identifier (lib/track-schema.ts issueViewCreateSchema). A lead reviewing workload per person or sorting by deadline cannot do it in the project view. First scope: groupBy (status, assignee, priority, cycle, label) for list and board, sort by due date and last updated, both persisted in saved views. Priority: medium. Effort: M. Compared with Linear.
- 0
Track: Search issue descriptions and comments, and escape LIKE wildcards
Linear search covers issue content and comments across the workspace (Cmd/Ctrl+F quick search, https://linear.app/docs/inbox). Track search only matches title or identifier (lib/track-data.ts listIssues and listAllIssues use title LIKE ? OR identifier LIKE ?), so you cannot find an issue by an error message pasted in its description. The query is also interpolated as %q% without escaping, so a search for 100% or snake_case matches unexpected rows. First scope: include description text and comment bodies in the search (SQLite FTS5 table or LIKE with ESCAPE), and escape % and _ in user input. Priority: medium. Effort: S. Compared with Linear.
- 0
Track: Add snooze and remind-me to the inbox and issues
In Linear, H snoozes an inbox item until a preset or typed time and new activity cancels the snooze; Remind me sends an inbox notification at a chosen time without hiding the issue (https://linear.app/docs/snooze). Track's inbox (components/track/InboxClient.tsx) only supports read and mark-all-read, with no snooze or reminder fields. Small teams use reminders to follow up on blocked work instead of keeping a separate to-do list. First scope: snoozed_until on notifications with presets (later today, tomorrow, next week), and a Remind me action on the issue that schedules a notification via the existing cron. Priority: medium. Effort: S. Compared with Linear.
- 0
Track: Support recurring issues on a daily, weekly, monthly or yearly schedule
Linear lets you make an issue recurring (daily, weekly, monthly, yearly); the next instance is created when the previous one hits its due date, and recurring issues are managed in team settings (https://linear.app/changelog/2024-12-05-recurring-issues, https://linear.app/docs/ops-and-marketing). In Track the only route is building a Flow with a schedule trigger and the app.track_issue action (lib/flow-schema.ts), which is far from the issue itself. Ops chores like invoicing, backups or monthly reports are a core small-team use. First scope: a Make recurring option on an issue with a frequency, stored rule, and a cron that clones title, description, labels and assignee with the next due date. Priority: medium. Effort: M. Compared with Linear.
- 0
Track: Add issue templates per project with preset properties and description
Linear templates preset properties and description, can be form templates with required fields, and a team can set a default template for new issues and for integrations (https://linear.app/docs/issue-templates). Track has no template concept: QuickIssueModal (components/track/QuickIssueModal.tsx) always starts blank and createIssue in lib/track-data.ts takes no template. Bug reports from teammates arrive without repro steps or environment. First scope: per-project templates (title prefix, description, labels, priority, status), a picker in the new-issue modal, and an optional default template, also applied to chat and flow sources. Priority: medium. Effort: M. Compared with Linear.
- 0
Track: Add Cmd+K command menu and single-key shortcuts for issue properties
Linear is driven by a command menu and single-key actions: S status, A assign, P priority, L labels, G then I for inbox, H snooze, and ? opens a searchable shortcut help (https://linear.app/docs/inbox, https://linear.app/changelog/2021-03-25-keyboard-shortcuts-help). Track only handles C, J/K and Enter (components/track/TrackShortcuts.tsx). Without property shortcuts, triaging a list means opening every popover with the mouse. First scope: on the focused row or open issue, S/A/P/L open the existing inline editors from components/track/InlineEditors.tsx, plus Cmd+K with go-to and change-property commands and a ? help dialog. Priority: medium. Effort: M. Compared with Linear.
- 0
Track: Create cycles automatically on a cadence and roll over unfinished issues
Linear creates upcoming cycles automatically with a 1 to 8 week length and start day, auto-adds started issues to the current cycle, rolls unfinished issues forward and keeps a scope/progress graph per cycle (https://linear.app/docs/use-cycles). Track cycles are created one by one by hand (cycleCreateSchema in lib/track-schema.ts, components/track/CyclesPanel.tsx) and rollover only happens when someone clicks Complete. Teams forget to create the next sprint and the overview shows No cycle. First scope: per-project cycle settings (length, start weekday, how many upcoming), a daily cron that creates future cycles and completes ended ones with rollover, and estimate-based progress in CyclesPanel. Priority: high. Effort: M. Compared with Linear.
- 0
Track: Expose issues, projects and comments in the public /api/v1 with webhooks
Linear's public GraphQL API covers issues, projects, cycles, labels, comments and relations, plus webhooks for every entity (https://linear.app/developers, https://linear.app/developers/webhooks). Our public API (app/api/v1) covers agents, calendar, crm and links but has no track resource; app/api/track/* only accepts session auth. Teams cannot script imports, sync with other tools, or let CI open issues. First scope: /api/v1/track/issues (list, get, create, update), projects and comments, with API key scopes from lib/api-auth.ts and entries in openapi.json; reuse the generic webhooks table for issue.created and issue.updated. Priority: high. Effort: M. Compared with Linear.
- 0
Track: Send email notifications and a daily digest for Track activity
Linear delivers notifications by desktop, mobile, Slack and urgency-timed email digests, configurable per type (https://linear.app/docs/notifications). Track notifications only exist in the in-app inbox (components/track/InboxClient.tsx, lib/notifications.ts has no email path for track types), so anyone not looking at the app misses assignments and mentions. For small teams that live in email, this is the main reason issues go stale. First scope: per-user setting for immediate email on assigned and mention, plus an optional daily digest of unread Track notifications, sent with the existing system sender. Priority: high. Effort: M. Compared with Linear.
- 0
Track: Let users subscribe to issues and notify all subscribers on changes
Linear auto-subscribes creators, assignees and mentioned users, allows manual subscribe/unsubscribe (Shift+S) and notifies every subscriber (https://linear.app/docs/notifications). Track hardcodes recipients: status changes go to assignee and creator, comments to mentions, assignee and creator (lib/notifications.ts, lib/track-data.ts createIssueComment), with no subscriber table. A reviewer or stakeholder who wants to follow an issue has no way to do it, and the creator cannot opt out. First scope: track_issue_subscribers table, auto-subscribe on create, assign, mention and comment, a Subscribe toggle on the issue page, and route all Track notifications through it. Priority: high. Effort: M. Compared with Linear.
- 0
Track: Add a Markdown rich text editor for issue descriptions and comments
Linear's editor converts typed or pasted Markdown into rich text, supports code blocks, attachments via /file and links @ENG-123 mentions as related issues (https://linear.app/docs/editor). Track stores descriptions as a single text block edited in a plain textarea (components/track/IssueDetailClient.tsx parseDescription, track-description-input), and comments are plain text. Bug reports and specs need headings, lists, code and inline images to be readable. First scope: reuse the Docs editor or a lightweight Markdown renderer for descriptions and comments, with code blocks, lists, links and pasted images uploaded as attachments; auto-link SLUG-N references. Priority: high. Effort: M. Compared with Linear.
- 0
Track: Let authors edit and delete their own issue comments
Linear lets you edit or delete your own comment from its overflow menu and resolve threads (https://linear.app/docs/comment-on-issues). In Track, app/api/track/issues/[id]/comments/route.ts only exposes GET and POST; deleteIssueComment in lib/track-data.ts is never called, and the comment body is also copied into the activity meta, so a typo or a leaked secret stays forever. commentCreateSchema (lib/track-schema.ts) also has no min length, so the API accepts empty comments even though the UI disables the button. First scope: PATCH and DELETE on /api/track/issues/[id]/comments/[commentId] restricted to the author, render the comment from track_issue_comments instead of activity meta, show an edited marker, and require body min(1). Priority: high. Effort: S. Compared with Linear.
- 0
Track: inline tasks, checkboxes and drag & drop
Add tasks inline or with C, check them off, edit in place and drag across the board. Plus a My tasks view.