Linear Cycles
Cycles are Linear's version of sprints. A cycle is a fixed block of time — usually one or two weeks — during which a team commits to completing a specific set of issues. Cycles create a rhythm that helps teams plan consistently, measure progress, and improve over time.
The Cycle Concept Explained
Think of a cycle like a weekly meal prep session. You plan what to cook on Sunday, you cook during the week, and at the end of the week you evaluate what worked and what didn't. The next week, you plan again with that knowledge.
CYCLE TIMELINE
Week 1 ─────────────────── Week 2
│ │
▼ ▼
Plan Do Review
│ │ │
│ │ │
Pick issues Work on them What got done?
for cycle each day What carried over?
│ │
▼ ▼
Close issues Start next cycle
Create a Cycle
Open your team view and click Cycles in the left panel. Click New Cycle to create one.
Cycle Creation Fields
| Field | Description | Example |
|---|---|---|
| Cycle Name | A label to identify this cycle | Sprint 24 or Week of Jun 16 |
| Start Date | When the cycle begins | June 16 |
| End Date | When the cycle ends | June 29 |
Linear can also auto-create cycles on a recurring schedule. Enable this in Settings > Teams > [Team] > Cycles. Set the default cycle length, and Linear creates the next cycle automatically when the current one ends.
Add Issues to a Cycle
Drag and drop issues from the backlog into the current cycle, or open an issue and change the Cycle property in the right panel.
Select multiple issues at once from the issue list to add them to a cycle in bulk. Right-click the selection and choose Add to Cycle.
How to Choose Issues for a Cycle
| Question to Ask | If Yes | If No |
|---|---|---|
| Is this issue Urgent or High priority? | Add to the cycle | Consider for next cycle |
| Can this be realistically finished in the cycle? | Add to the cycle | Break it into sub-issues first |
| Does this issue have all information needed to start? | Add to the cycle | Keep in backlog until it's clearer |
| Is someone available and assigned to do this? | Add to the cycle | Assign first, then add |
Active Cycle View
The active cycle view shows all issues committed to the current cycle. The top of the page displays a progress bar showing the percentage of issues completed.
┌───────────────────────────────────────────┐ │ Sprint 24 | Jun 16 – Jun 29 │ │ │ │ Progress: ██████░░░░░░ 8 / 14 done │ │ │ │ Assignee Breakdown: │ │ Alice: 4 done / 3 remaining │ │ Bob: 2 done / 2 remaining │ │ Carlos: 2 done / 1 remaining │ └───────────────────────────────────────────┘
Cycle Cooldown Period
Linear recommends a short cooldown between cycles — typically one day. During cooldown, the team:
- Marks any final completed issues as Done
- Reviews what wasn't finished and decides whether to roll it into the next cycle
- Identifies recurring patterns like persistent blockers or overcommitted cycles
Carry Over Unfinished Issues
When a cycle ends, Linear prompts you to handle unfinished issues. You choose what happens to each one.
| Option | What Happens | When to Use |
|---|---|---|
| Move to Next Cycle | Issue appears in the next cycle automatically | Work is partially done and still relevant |
| Move to Backlog | Issue returns to the backlog | Work was not started or is no longer urgent |
| Cancel | Issue is marked as Cancelled | The task is no longer needed |
Cycle Analytics
After a cycle ends, Linear generates a summary showing how much was planned versus completed. This data appears in the cycle history under the Cycles section.
| Metric | What It Shows |
|---|---|
| Completion Rate | Percentage of committed issues closed |
| Scope Added | Issues added after the cycle started |
| Velocity | Total estimate points completed per cycle |
| Carry Over Rate | How many issues rolled to the next cycle |
Review these metrics before planning the next cycle. A consistently high carry-over rate means the team is over-committing. Reduce the planned load and build in buffer time.