Cycles are numbered, fixed-length iterations for your workspace — a sprint cadence without the ceremony. Once enabled, cycles are generated on a schedule, advance on their own, and carry unfinished tasks forward when they end. You never create or close a cycle by hand.
Cycles work on Tasks: assign tasks to a cycle, filter and group the task list by cycle, and watch progress on the Cycles page.
How cycles work
- Each cycle has a number, a name, and a start/end date. Numbers count up per workspace and are never reused, even after schedule changes.
- A cycle’s state comes from its dates: Upcoming before the start date, Active between start and end, Completed after the end date. There is no manual open/close.
- Once a day (shortly after midnight UTC), Rollout provisions the configured number of upcoming cycles, rolls unfinished tasks out of ended cycles, and records progress stats for active cycles.
Turning on cycles
Cycles are off by default. A workspace owner or admin enables them:
- Go to Settings > Cycles or navigate to /settings/cycles
- Turn on Enable cycles
The first cycles are provisioned immediately, starting on the next occurrence of the configured start day.
Schedule settings
The schedule lives on the same page. Change values and click Save schedule.
| Setting | Description |
|---|---|
| Cycle length | 1–8 weeks (default 2) |
| Start day | Day of the week each cycle starts (default Monday) |
| Cooldown between cycles | 0–4 weeks off between cycles (default none) |
| Upcoming cycles to keep ready | How many future cycles stay provisioned, 1–6 (default 2) |
| Roll over unfinished tasks | Move incomplete tasks into the next cycle when a cycle ends (default on) |
| Add started tasks to the active cycle | A task moved into a started status without a cycle joins the active cycle (default on) |
| Name template |
Names for new cycles; {n} is replaced with the cycle number (default Cycle {n}) |
Schedule changes apply to future cycles only — the active cycle keeps its dates. Upcoming cycles that hold no tasks are regenerated against the new schedule on save; an upcoming cycle that already has tasks is left alone. The name template applies to newly created cycles.
Below the schedule, the Provisioned cycles section lists the active cycle and everything already scheduled.
Assigning tasks to a cycle
Three ways to put a task in a cycle:
- Task details: use the Cycle field in the task sidebar. The picker offers current and upcoming cycles plus the most recently completed one, or No Cycle to clear it. The field appears once cycles are provisioned.
- Bulk move: select multiple tasks in the task list and use Move to Cycle. Pick a cycle, or No cycle to remove the selection from their cycles.
- Automatically on start: with Add started tasks to the active cycle on, a task moved into a started status without a cycle joins the active cycle. An explicit cycle choice — including deliberately clearing the field — always wins.
Automatic rollover
With Roll over unfinished tasks on, tasks in an ended cycle that aren’t in a Completed or Canceled status move into the current cycle — or into the next upcoming one during a cooldown gap. Completed and canceled tasks stay where they finished, so each cycle keeps an accurate record of what shipped in it.
Every carried-over task gets an entry in its activity feed (“Rolled into the next cycle”), so you can see how often a task has slipped.
Turn the setting off to keep unfinished tasks in their original cycle and move them yourself.
The Cycles page
Open Cycles from the sidebar for the schedule at a glance. The page lists the active cycle first, then upcoming cycles, then recent completed ones, each with:
- Name and date range
- State badge (Active, Upcoming, or Completed)
- A completion bar with done vs. total task counts
Click any cycle to open the task list filtered to it. The header shows when the active cycle ends, and admins get a Configure shortcut to the settings page.
Note: canceled tasks drop out of a cycle’s progress — they don’t count toward its scope.
Filtering and views
On the task list, the Cycle filter leads with three moving options alongside the concrete cycles:
- Active cycle — the cycle containing today
- Previous cycle — the most recently ended cycle
- Next cycle — the next upcoming cycle
These resolve when the view loads, not when you save it. A saved view filtered to Active cycle advances on its own each time a new cycle starts — pin it in the sidebar as a permanent “current sprint” view. See saved views for how views work.
In table view, you can also group tasks by cycle via the grouping menu.
Troubleshooting
The Cycle field is missing from tasks
- Cycles aren’t enabled or provisioned yet. A workspace owner or admin can turn them on under Settings > Cycles.
No cycle is active right now
- With a cooldown configured, there are gaps between cycles. Tasks rolled over during a gap land in the next upcoming cycle.
A schedule change didn’t move the current cycle’s dates
- That’s by design: the active cycle always keeps its dates, and upcoming cycles that already contain tasks aren’t regenerated. The new schedule takes effect for future cycles.