Cycles
Time-box team issue work into iterations with current and upcoming cycles.
Cycles are a repeating time-box for a team's planned work, similar to sprints.
Cycles are time-boxed periods where a team works through a set of issues. When enabled, Pulse creates upcoming cycles for the team. They are not tied to releases.
Configure
Configure cycles under Settings → Your teams → <team> → Cycles. Turn on Enable cycles. Team managers and workspace admins can change the policy.
A child team can inherit its parent's cadence. Parent changes apply to future cycles; completed history stays as it was. Use Set own cadence if the child team should diverge.
When you first enable cycles, choose what to do with work already in progress: Keep work active, Move work to Backlog, or Leave existing work unchanged. That choice runs only on the save that turns cycles on.
Open Cycles from Your teams (G then C). The team sidebar also shows Current (G then V) and Upcoming (G then W).
Cycle settings
Cycle duration
In Cycle duration, choose how many weeks each cycle lasts (1–8). Cycles follow a repeating schedule. You can still move dates on an individual future cycle later.
Cooldown duration
Add a Cooldown duration after each cycle, or choose No cooldown. The cooldown must be shorter than the cycle. Issues are not assigned to a cooldown window.
Cycle start and timezone
Cycle start is the weekday every generated cycle begins. Boundaries use local midnight in Team timezone.
Auto-create cycles
Auto-create cycles sets how many future cycles Pulse keeps ready (1–15).
Disable cycles
Disable cycles completes the running cycle and freezes its metrics, removes generated upcoming cycles, and keeps completed history. You can enable cycles again later.
Adjust cycles
Move start and end dates
To move dates on a future cycle, use Move start date… or Move end date… in the overflow menu. The start date cannot change after a cycle has started. Completed cycle dates are locked. Cycle dates cannot be moved into the past.
See Update cycles for name, description, and how gaps show as cooldown or Cycles paused.
Start a cycle today
To kick off the next cycle early, open its overflow menu and choose Start cycle today. This starts the planned cycle today and keeps its current end date.
If another cycle is active, it completes and unfinished work rolls into the cycle you started.
Please note that you cannot undo Start cycle today.
Cycle automations
Issues rollover
Unfinished work rolls over during the hourly cycle sweep. Moving an issue to Backlog opts it out of rollover. There is no way to keep unfinished issues in a closed cycle.
Completing a cycle from the cycle page lets you pick a target cycle for remaining open issues.
Assign an issue to a cycle with Shift C, from the composer, or in bulk. An issue belongs to at most one cycle at a time.
Auto-add active issues to current cycle
- Started issues — add newly started issues to the current cycle. During cooldown they stay unassigned until the next cycle starts.
- Completed issues — attribute newly completed issues to the current cycle, or to the cycle that just ended during cooldown.
Cycle capacity
On Cycles, cycles that have not finished show a capacity ring: how much of the forecast the current scope uses.
Capacity comes from the last completed cycles' delivered work (up to three, in the team's estimate unit). If the team has no matching history, Pulse estimates from current team size. Completed rows show success instead of capacity.
Open a cycle to see the same forecast in the details sidebar, and the cycle graph for burndown.
FAQ
Last updated on