Linear is a purpose-built issue tracking and project management platform designed specifically for high-velocity software teams. Unlike legacy tools that evolved from traditional project management, Linear was built from the ground up for modern engineering workflows—featuring keyboard-first navigation, sub-100ms response times, and an opinionated design that eliminates configuration overhead. At its core, Linear organizes work into issues (individual tasks), projects (cross-team features with milestones), and cycles (time-boxed sprints), all accessible through a blazing-fast interface that prioritizes speed over customization. The key mental model: Linear doesn't ask how you want to work—it shows you how high-performing teams structure their workflow, from automatic triage to synchronized Git commits, enabling teams to ship faster by reducing the friction between planning and execution.
What This Cheat Sheet Covers
This topic spans 30 focused tables and 197 indexed concepts. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.
Table 1: Core Concepts and Work Units
Everything in Linear nests inside a clear hierarchy of work units, and understanding how they relate is the foundation for everything else. Issues are the atomic tasks, cycles are the time-boxed sprints that contain them, projects bundle issues toward a deliverable, initiatives group projects into strategic themes, and teams and workspaces are the organizational containers above it all.
| Concept | Example | Description |
|---|---|---|
Create issue: CENG-1234: Fix login bug | • Fundamental unit of work — a single task, bug, or feature request • each has a unique identifier, status, assignee, and priority | |
Project: "Mobile App v2.0"Timeline: 6 weeks, 3 milestones | • Cross-team deliverable with a clear outcome or planned completion date • contains issues and milestones • use for features that span multiple sprints | |
Initiative: "Enterprise Readiness"Groups 5 projects across teams | • High-level strategic goal that groups multiple related projects • provides leadership visibility into themes without adding project overhead | |
2-week cycle: Jan 15–29Auto-creates every 2 weeks | • Time-boxed sprint for planning and executing work • issues added to cycles appear in team views • configurable duration and auto-creation |