Linear review: issue tracking, cycles and roadmaps for software teams

What Linear is

Linear tracks the work of product and engineering teams. The unit of work is the issue. Issues belong to teams, can be scheduled into cycles, and can be grouped into projects, which in turn roll up into initiatives.

Linear is more opinionated than a general work management tool. Cycles repeat on a fixed schedule, projects are meant to have a clear outcome, and issue status can follow pull request and merge request activity. That suits software teams, and it is a constraint for teams whose work is not code.

How work is organized

A workspace contains teams, and each team has its own issues and workflow settings. Issues carry properties such as status, assignee, priority, labels, due date and an estimate, and can have sub-issues. Display options control which of these show on each issue in a list or on a board card.

Issue views switch between list and board layouts, and can be grouped by status, assignee, project, priority, cycle, label and other properties. Board views can add sub-groups as rows for a swim-lane layout.

Cycles

Cycles are Linear's version of sprints. Linear's docs describe them as time-boxed periods that are not tied to releases. A team turns them on in its settings, picks a length of one to eight weeks and a start day, and Linear creates upcoming cycles automatically, up to 15 ahead.

• Open issues that are unfinished when a cycle ends generally roll over into the next cycle automatically.
• An optional cooldown period after each cycle leaves time for technical debt and planning; issues cannot be assigned to a cooldown.
• Cycles that have not started show a capacity estimate based on the work completed in the previous three cycles.
• Sub-teams inherit their parent team's cycle schedule, which keeps several teams on the same cadence (sub-teams start on Business).

Triage and intake

Triage is a team inbox. Issues created through an integration such as Slack or Sentry, or by someone outside the team, land there first. From Triage you accept, decline, mark as duplicate or snooze each issue. Triage itself is on every plan.

Triage rules, which set team, status, assignee, label, project or priority automatically, and Triage responsibility, which rotates who watches the queue, are on Business and Enterprise. So is Triage Intelligence, which uses AI to suggest properties and flag likely duplicates. Linear Asks, for taking requests from people who do not use Linear, starts on Business.

Projects, roadmaps and initiatives

A project groups issues with a clear outcome or planned completion date, such as a feature launch. Projects can be shared across teams, have milestones, and hold documents written in the same Markdown as issues. An issue can belong to only one project at a time. Each team's Projects page shows projects as a list, board or timeline, and a workspace-level Projects page shows them all.

Linear renamed its roadmaps to initiatives. An initiative groups projects around a company objective, with a status (Proposed, Planned, Active, Completed or Canceled), an owner and a target date. Its health column reflects the latest update, and an Active projects column rolls up each project's latest update as on track, at risk or off track. Team initiatives are on Business and Enterprise; sub-initiatives and saved initiative views are Enterprise only.

For reporting, the pricing page lists progress reports on every plan, Insights from Business and Dashboards on Enterprise.

GitHub, GitLab and other integrations

The GitHub integration links pull requests to issues through branch names, PR titles or magic words, and links commits through magic words in commit messages. Issue statuses then update automatically as PRs and commits move, with rules that can differ by target branch. GitHub Issues can be synced one way or both ways, and older GitHub issues can be imported. Diffs lets reviewers look at code changes inside Linear.

The GitLab integration links merge requests to issues, for example through a magic word such as "Fixes ENG-123" in the MR description, for hosted GitLab and for self-hosted installations that are publicly reachable. It updates issue status as MRs are drafted, opened, reviewed and merged, with branch-specific rules. Two limits from Linear's docs: GitLab MRs cannot be linked through commit messages, and a workspace can connect only one GitLab instance.

Support integrations with Zendesk and Intercom are on Business and above, and API and webhook access is on every plan.

Plans and what needs a paid tier

We do not publish prices because they change. Check Linear's pricing page for current numbers. The capability split we found on 19 October 2026:

• Free: unlimited members, 2 teams, 250 issues and 10MB file uploads, with issues, projects, cycles, initiatives, Triage, integrations and the Linear Agent included.
• Basic: 5 teams, unlimited issues and unlimited file uploads.
• Business: unlimited teams, private teams and guests, Triage rules and Triage Intelligence, Issue SLAs, Linear Insights, Linear Asks, and Zendesk and Intercom integrations.
• Enterprise: annual billing only, SAML and SCIM, sub-initiatives, Dashboards, audit log, Advanced org modeling, and migration and onboarding support.

On Free, check the 250-issue cap against the size of your backlog before you import it. Some AI features, including Loops and coding sessions, also need AI credits on top of the plan.

Who Linear fits

Linear suits software teams that work in repeating cycles, keep their code in GitHub or GitLab, and want issue status to follow pull request activity instead of manual updates. Initiatives also give leads one view of project health across teams.

Who should look elsewhere

• If your projects are not software projects, such as marketing campaigns, events or client work, a general project tool may match your work more closely.
• If you need Gantt charts or native time tracking, we did not find either in Linear's docs or pricing page. Linear offers timeline views for projects and point estimates for issues.
• If you use GitLab issues today, note that Linear's migration assistant does not import them; its docs suggest the CLI importer or a CSV export instead.
• If you need private teams or guest accounts, plan for Business from the start.

How to trial Linear

Set up one team, turn on cycles with your usual sprint length, and connect your GitHub or GitLab repository. Create a project for a real piece of work, add a few milestones, and use magic words in pull requests so you can see issues move without manual updates.

Turn on Triage and route one intake source into it. Free allows 250 issues, which is enough for a short trial; if your backlog is larger, test on Basic instead.