How To Use Cycles In Linear

Learn how to enable cycles and get started with them in 60 seconds.

Linear helps streamline software projects, sprints, tasks, and bug tracking. It’s built for high-performance teams.

[JanacMeena]

- Cycles, similar to sprints in Agile methodologies, allow teams to focus their priorities over a set time period, and are enabled through team settings.
- Once enabled, a cycle section appears in the team's sidebar, and issues can be added directly to any cycle by pressing specific keyboard shortcuts or from the cycle icon.
- Active issues and those planned for upcoming cycles can be found from the sidebar, and cycles can be customized to rename, adjust the cooldown period, or sync with a chosen calendar.
- The progress of cycles can be tracked in the cycles pane, including a graph showing cycle time, effort, scope, and completion percentage; individual team members' progress can also be tracked.
- Unfinished issues from the current cycle will automatically roll over to the next cycle, and more details on cycles, keyboard shortcuts, and other information can be found in the documentation.

[xuedalong]

I don’t want to have to assign items to cycles (that’s just extra work for me and potentially dishonest guesswork). I just want to be able to track average velocity on a weekly basis while I continue to churn down my product backlog. Can I do that in linear?

[serhey]

is there a time tracker in this app and how to find/turn on it?

[isaiah]

Sprints aren't supposed to be necessarily tied to releases. That is a big misconception about agile and a red flag that maybe this is just marketing jargon/nonsense. Are there actual relevant differences from sprints?