Linear Workflow in Practice — Complete Guide to Issues, Cycles, Projects & Roadmaps [2026]

Linear's workflow flows through five stages: Triage → Backlog → In Progress → In Review → Done. New requests land in Triage for evaluation, move to Backlog once prioritized, enter In Progress when a developer pulls them into a Cycle, pass through In Review during code review, and land in Done on merge. Each Linear feature — Issues, Cycles, Projects, and Roadmaps — plays a specific role in keeping this pipeline running smoothly.

Issues are Linear's atomic unit of work. Beyond a simple title, each Issue supports rich metadata to structure and prioritize work.

Sub-issues let you decompose large tasks into granular steps while the parent Issue aggregates overall progress automatically.

Cycles are Linear's sprint feature, supporting any interval from 1 to 8 weeks. You can create Cycles manually or configure auto-generation (e.g., a new Cycle starts every Monday). Capacity planning: Assign Story Points to Issues to visualize total capacity vs. committed work in real time, preventing overcommitment and stabilizing team velocity. Automatic rollover: Incomplete Issues at the end of a Cycle are automatically rolled over to the next one (configurable). No manual housekeeping — what's unfinished is always visible and accounted for.

Projects group related Issues around a shared goal or deliverable — ideal for cross-sprint initiatives like "v2.0 Release" or "Checkout Redesign". Key Project features: - Milestones: Define phases or target release dates within a Project - Progress bar: Auto-calculated from completed vs. total Issues - Project owner: Assign a single accountable person to avoid committee decisions - Documents: Attach PRDs, specs, and meeting notes directly to the Project - Cross-team: Engineering and Design share the same Project for seamless collaboration While Cycles track velocity over time, Projects track completion of a defined deliverable. Both are complementary and used simultaneously.

Roadmaps (available on paid plans) display multiple Projects on a shared timeline, connecting strategic quarterly goals to day-to-day engineering.

With Roadmaps, PMs can share a single Linear URL with executives instead of maintaining separate slide decks — the data is always live.

Linear's native GitHub integration eliminates nearly all manual status updates during development. Branch naming: Click "Copy Git Branch" on any Issue to get a pre-formatted branch name (`<username>/<issue-id>-<title>`). Using this name automatically links the PR to the Issue. Automatic status transitions:

Add `Fixes LINEAR-123` to any commit message to link it to an Issue. Developers never need to manually update Issue status again.

Linear's Slack integration keeps the team informed without requiring context switches. What you can do: - Receive notifications in Slack channels for new Issues, status changes, and comments - Create Issues directly from any Slack message using the message action menu - Mention `@Linear` to view Issue details inline in Slack - Filter notifications by label, priority, team, or assignee to reduce noise Setup: Linear Settings → Integrations → Slack → Select channel → Configure notification rules. Once connected, your daily standup can begin in Slack without anyone needing to open Linear first.

The Linear Method (linear.app/method) is a publicly available set of principles for how high-performing software teams should operate. Core tenets include: 1. Cycle-driven development: Maintaining a consistent build-measure-learn rhythm improves predictability and team velocity. 2. Project ownership: Every project has one accountable owner. Committee ownership dilutes responsibility and slows decisions. 3. Write to think: Well-written Issues and Project descriptions create shared understanding. The goal is Issues that are self-explanatory without verbal supplements. 4. Preserve simplicity: Resist the temptation to add custom fields and complex workflows. Every addition increases cognitive overhead. Adopting the Linear Method improves not just tool usage but the underlying engineering culture — resulting in faster shipping and fewer coordination failures.

Q1. What's the difference between Cycles and Projects? Cycles are time-boxed sprints (e.g., 2-week repeating intervals). Projects are goal-based groupings (e.g., Authentication v2). A single Project typically spans multiple Cycles. Q2. When should I use Triage? Triage is for Issues that haven't been prioritized yet — incoming bugs, ad hoc requests, or ideas that need evaluation. A weekly Triage review session keeps Backlog clean. Q3. How do you manage Issues across multiple teams? Issues belong to a specific team, but Projects and Roadmaps provide cross-team visibility. Use Issue Relations (blocks/blocked by) to surface inter-team dependencies. Q4. Can I connect an entire GitHub Organization to Linear? Yes. You can connect all repositories in a GitHub Organization, or limit the integration to specific repos. Q5. Where do I see team velocity in Linear? The Cycles list view shows completed Issues and points per Cycle. The Insights page displays velocity trends as charts across historical Cycles. Q6. Do I need a paid plan for Roadmaps? Yes — Roadmaps require the Standard plan or above (starting at $9/user/month). Smaller teams can approximate Roadmaps using Project progress views and Cycle planning.

Once your Linear foundation is in place, the next step is connecting it to AI agents, GitHub Actions, and internal tooling to further amplify engineering throughput. Oflight's engineers support teams end-to-end: from Linear workflow design and GitHub/Slack integration to custom automation and team training. Explore AI Consulting Services