Cycles on a schedule. Rollover you can review.
Set a cadence for the whole workspace or for each application. Cycles appear ahead of time, unfinished work moves on the way you decide, and capacity shows who can take more before you commit.
One cadence per project, if you want one
A client app on one-week cycles and an internal tool on three-week ones can live in the same workspace. Each schedule sets a length of 1 to 56 days, a cooldown of up to 28 days, how many cycles to plan ahead (1 to 12), and how cycles are named and numbered.
- Workspace-wide cycles or project-owned cycles
- Project cycles only accept that project's tickets
- Cycle goals, and a preview before saving a schedule
2-week cycles · 0 unfinished carried to Cycle 24
Nothing silently falls between two cycles
When a cycle ends, preview what is unfinished and choose what moves. Or switch on automatic rollover — unfinished work only, or including Triage — and let the schedule worker do it for you.
- Reviewed rollover with a preview
- Automatic modes: off, unfinished, including Triage
- Available to agents too: preview_cycle_rollover, rollover_cycle
Automatic mode moves unfinished work — optionally including Triage — when the cycle ends.
Know who can take more
Each person has a capacity in points and an availability of Available, Busy or Away. Workload counts their assigned tickets and points, and saved views can show only the people who are available.
- Viewers and finished work are left out
- Zero-estimate tickets still count as assigned
- Overview: created versus completed over 7 days
Milestones counted from the work
Milestones carry a status, an owner and start and target dates. Progress is counted in tickets and points from what is attached — and they sit on the roadmap timeline next to your applications.
- Filter any view by milestone
- Releases and launches as milestones
- Roadmap timeline across projects
Set a cadence once, and keep it
Request access and we set up schedules for your applications with you.