Productivity & Workflows
Linear Cycle Rollover: Reconcile Unfinished Issues Before Planning the Next Cycle
An eight-issue fictional reconciliation separates carried work and Started automation from backlog, triage, cancellation and completion; a ten-point accepted plan keeps a two-point reserve and defers five-point N2.
After a Linear cycle closes, reconcile the issues that remain, the work still required, and the people available before treating the next cycle as an agreed plan. Rollover changes cycle membership; it does not confirm a new delivery commitment or erase an unresolved blocker. Check unassigned issues that enter through automation separately from work carried forward.
This LandOffer.ai guide uses eight fictional issues and a completed next-cycle capacity decision. Linear documentation was checked October 25, 2026. All issue records, effort estimates, settings, dates, owners, and outcomes are authored teaching examples. No Linear workspace, cycle, issue, automation, or calendar was accessed or changed. Offline arithmetic checks support the example totals, not a product test or delivery forecast.

Understand which mechanism puts an issue in a cycle
Linear's cycle guide separates unfinished assigned-issue rollover from optional automation adding Started or Completed issues that lack a cycle. During cooldown, its documented exceptions include closing-cycle items moved to Backlog, Triage, Canceled, or Completed. Started unassigned issues can enter the next cycle with the corresponding automation; completed unassigned issues are attributed to the previous cycle. Issues cannot belong to a cooldown, and cycles are not releases.
Use those distinctions to ask why a specific item appears in the next plan. Was it unfinished work already accepted earlier, newly started work caught by an automation, or an intentional new selection? An issue in the next cycle may still need its remaining scope and owner acceptance reviewed.
Record your team’s actual settings and the time at which you checked the issues. Do not infer an enabled automation from a colleague's screenshot or from another team's behavior. Review an individual issue's state and history when membership looks surprising, then preserve any uncertainty instead of editing it until the totals look tidy.
Changing settings is a separate decision. A reconciliation should explain the current record before proposing a new policy. Keep newly captured work visible so its owner can explain the scope and the team can decide whether to accept it.
Reconcile identity, remaining work, and evidence
For each issue, retain its stable identifier, closing-cycle state, later changes, next-cycle membership, current owner, and remaining acceptance work. A title is not enough: a reopened issue may share its original title while requiring a different correction. A duplicate may resemble a second deliverable but point to the same underlying work.
Linear's issue-properties documentation describes team-specific workflow states, relations, and estimates representing complexity or size. An estimate is not a measurement of hours already spent or proof that the remaining work fits. Use a consistent team convention and reassess scope before adding whole estimates together.
Separate completion evidence from an issue's label. “Done” may mean the agreed issue acceptance criteria were met; it does not establish every dependent activity is finished. Ask whether the reviewed change is merged, documented, released, or available to its intended audience according to the actual task. Preserve whatever remains outside that particular issue's acceptance.
Do the same for blocked work. A blocker does not become available because the issue crossed a cycle boundary. Name the dependency owner and the evidence needed to unblock it. If that person has not accepted a date, keep the plan conditional rather than translating the cycle's end into their commitment.
Worked reconciliation of eight fictional issues
The fictional Beacon team closes cycle C14 on November 13, 2026. Its recorded cooldown is November 16–20, followed by C15 starting November 23. These are stipulated planning dates, not a demonstration of Linear's date engine or a live boundary transition. Team lead Selma and coordinator Joel review the record at the end of cooldown.
The example assumes the automation for Started issues without a cycle is enabled. Case labels B1–B8 identify eight authored records, not live issue links. B1–B7 were associated with the closing cycle; B8 had no cycle when work started. The table’s outcomes are author-written examples of the documented distinctions, not records returned by Linear.
| Issue and work | Closing record or later change | C15 disposition in the fictional record | Evidence and owner decision |
|---|---|---|---|
| B1: Correct a missing hint label | Completed before C14 closes | Not unfinished carryover | Reviewer accepted the label correction; release availability is not established by this issue record |
| B2: Repair empty-state guidance | Started and unfinished; remains open through cooldown | Carried work | Mara accepts three remaining planning points for correction, review and documentation; she preserves the outstanding reviewer question |
| B3: Add a shared filter example | Unstarted in C14, still open | Carried work | Dev confirms two remaining points and the unchanged acceptance example |
| B4: Explore an optional visual theme | Moved to Backlog during cooldown | Excluded from next-cycle carryover | Selma records deliberate deferral; no claim that the exploration was completed |
| B5: Investigate a new report | Moved to Triage during cooldown | Excluded from next-cycle carryover | Ayla must determine scope before estimating; not a zero-effort task |
| B6: Build an obsolete menu variant | Canceled during cooldown after owner review | Excluded from next-cycle carryover | Cancellation reason retained; canceled work is not reported as a delivered feature |
| B7: Finish checklist wording | Completed during cooldown | Not carried into C15 | Joel retains the completed wording record and its closing-cycle context; it is not new C15 output |
| B8: Repair an export-message typo and linked explanation | Started during cooldown without a cycle | Enters C15 through the enabled Started automation | Ayla identifies three remaining points; appearance in C15 does not mean Selma previously accepted it |
Eight records reconcile to three C15 items and five outside that next-cycle set. Of the three, B2 and B3 are carried work; B8 arrived through separate automation. Selma must review B8 as previously unassigned work even though it now appears beside the two carried items. The other five have distinct dispositions that should remain visible in the review record.
The team does not force excluded items into a guessed common state. Backlog, Triage, Canceled, and completed work answer different questions. Joel preserves each source issue's actual association and history in a real reconciliation rather than claiming this table specifies every field Linear would retain after each transition.
No new issue is created merely because an old one rolled. B2 keeps its identity and links to earlier work. Mara's three remaining points include the unresolved review, rather than counting only the small code edit and leaving review capacity elsewhere unrecorded. B5 remains unestimated; it is excluded from the commitment until its scope is understood.
Joel also records the review cutoff and who supplied each decision. A change made after that cutoff belongs in a dated amendment, with its reason and effect on remaining scope. The original reconciliation remains available for comparison. If another team owns a dependency, Joel records its accepted contribution separately instead of assigning that team's entire task to Beacon's capacity. This keeps a cross-team handoff visible without counting the same work twice or implying that a local cycle selection binds people who were not part of the planning decision.
Build the next plan from accepted remaining work
Joel prepares the second worked asset: the C15 planning ledger. The team's fictional internal allowance is twelve planning points after known leave, recurring support duties, and review availability. This is an agreed planning assumption in the story, not a number calculated by Linear or a conversion of points to staff hours.
The proposal initially contains B2, B3, B8 and two newly requested items, N1 and N2. N1 is a two-point example-format correction; N2 is a five-point optional layout experiment. N1 and N2 are new authored proposals outside the original eight-record reconciliation. Keeping those populations separate prevents a changing denominator from looking like a counting mistake.
| Proposed work category | Item and accepted remaining estimate | Capacity decision and responsible person |
|---|---|---|
| Carried work | B2, three points | Mara accepts the remaining scope, including the reviewer question and documentation; conditional on the named review route |
| Carried work | B3, two points | Dev accepts the unchanged example scope |
| Captured unassigned work | B8, three points | Ayla explains why work began; Selma now explicitly accepts its remaining scope rather than treating automation as approval |
| New selected work | N1, two points | Dev accepts after confirming capacity alongside B3 |
| New requested work | N2, five points | Defer outside C15; no owner acceptance is implied by the request |
| Reserved allowance | Two points of the twelve-point allowance | Keep unallocated for review discoveries; this is not another completed issue |
The accepted work totals ten points: five carried, three from the previously unassigned item, and two new. The two-point reserve brings the internal allowance to twelve. Accepting N2 as well would require fifteen points of work before any reserve, exceeding the stated allowance by three. Selma records the deferral rather than hiding it inside an optimistic total.
This is a planning decision with remaining conditions. Mara's reviewer has accepted a review route but has not resolved the question itself. If the answer expands B2's scope, the team must revisit the ledger. A larger review finding or another absence could exceed the two-point reserve and require a changed plan.

Record the plan without turning a cycle into a release
Selma's completed fictional handoff reads:
C15 contains two carried items, B2 and B3, plus B8 captured through the Started automation. We have now reviewed and accepted those remaining scopes. We also select N1. Accepted work is ten planning points against a twelve-point internal allowance, leaving two unallocated. N2 is deferred; B5 still needs triage and is not silently included.
Mara owns B2's reviewer follow-up; Dev owns B3 and N1; Ayla owns B8. Joel retains the eight-record reconciliation and capacity ledger. If a blocker, estimate, or availability changes, bring that change to Selma before presenting an expanded plan as agreed. This record does not approve a production release or promise a completion date for an unaccepted dependency.
The handoff is complete as written text; no issue update, assignment, notification, or coworker message was sent. Its value is a usable baseline: which work is included, how it arrived, who accepted it, what was deferred, and what reopens the decision.
Linear's projects guide describes projects as groups of issues with a clear outcome or planned completion date. Use the relevant project and release records to assess the broader result. Finishing an issue set in a cycle does not prove the feature is available, the rollout is complete, or the intended customer outcome occurred.
Explain metrics with their population and observation time
Linear documents cycle capacity as an estimate based on the previous three completed cycles, with a rough member-based estimate when there is no completed history. It also says a completed cycle's historical graphs can differ from its later issue list. Those are useful reasons to retain a dated snapshot instead of treating a current list as a permanent statement about past work.
If your team uses a capacity indicator, record what it represents and compare it with present availability and scope. Do not call the fictional twelve-point allowance a product forecast, or infer that a point total guarantees effort, quality, or delivery. Changes to estimates and issue states need explanation alongside any changed total.
For the next rollover, reconcile stable issue identities first, then separate carried work, captured unassigned work, new requests and explicit deferrals. Ask each owner to accept the stated remaining scope, record unresolved dependencies, and identify who will revisit an affected commitment. Further workplace guides from LandOffer.ai can support that review; save the reconciled record and accepted capacity decision before calling the next cycle planned.


