This set builds vocabulary for describing sprint-style cycle planning and milestone tracking in Linear.
0 / 5 completed
1 / 5
At standup, a dev mentions the team's fixed-length iteration for planning and tracking a batch of issues in Linear. What is this called?
A cycle in Linear is a fixed-length time period, similar to a sprint, during which a team commits to and tracks a defined set of issues. It provides a recurring cadence for planning and reviewing progress. This differs from a milestone, which marks a specific deliverable rather than a recurring time box.
2 / 5
During a design review, the team groups related issues under a specific deliverable target, like a feature launch, independent of any single cycle. What is this grouping called?
A milestone groups issues toward a specific deliverable or launch target, which may span multiple cycles rather than being tied to one fixed time box. This lets a team track progress toward a larger goal independently of sprint-length iteration boundaries. Milestones and cycles serve complementary but distinct planning purposes.
3 / 5
In a code review, a dev references an issue that automatically moved to the next cycle because it wasn't completed in time. What is this behavior called?
Cycle rollover automatically carries an incomplete issue into the next cycle rather than leaving it stranded in a closed one, keeping the backlog accurate without manual re-triage of every unfinished item. This automation reduces planning overhead between iterations. It reflects a common pattern in sprint-based issue tracking generally.
4 / 5
An incident report shows a team consistently rolled over the same large issue across several cycles without completing it. What planning gap does this suggest?
Repeated rollover of the same issue across multiple cycles is a common signal that the work item is too large or poorly scoped to fit within a single iteration. Breaking it into smaller, independently completable pieces usually resolves the recurring rollover. This is a standard diagnostic when reviewing cycle health in sprint-based planning.
5 / 5
During a PR review, a teammate asks how a cycle differs from a milestone in Linear's workflow model. What is the distinction?
A cycle structures work around a recurring, fixed-length time period, while a milestone tracks progress toward a specific outcome that may span multiple cycles. Using both together lets a team manage short-term iteration cadence and longer-term deliverable tracking simultaneously. This separation of concerns is common across modern issue-tracking tools.