Cycles

Cycles time-box issue work for a team — similar to sprints in agile workflows. Teams opt in through settings; until cycles are enabled, cycle views stay hidden.

When to use cycles

Use cycles when a team:

• Plans work in fixed-length iterations
• Needs Current and Upcoming views in the sidebar
• Tracks scope, started, and completed points using estimates
• Wants burndown-style progress within an iteration

Teams that flow continuously without iterations can leave cycles disabled.

Enable cycles

Team managers and workspace admins:

1. Go to Settings → Your teams → <team> → Cycles.
2. Turn cycles on and set duration, start day, and automations.
3. Save.

Sub-teams configure cycles independently — settings do not inherit from a parent team.

If Cycles does not appear under a team, the workspace cycles capability may be off or cycles are disabled for that team.

Current and upcoming

When cycles are active, the team sidebar expands Cycles:

• Current — the active iteration (/cycles/current?team=…)
• Upcoming — the next planned iteration

Assign issues to a cycle from the issue composer or bulk actions. Issues can belong to at most one active cycle per team.

Planning a cycle

Typical flow:

1. Open Upcoming (or the next cycle page).
2. Filter backlog issues by priority and estimate.
3. Move selected issues into the cycle.
4. Confirm scope against team capacity when estimates are enabled.

Estimate behavior: Estimates.

Completing a cycle

When an iteration ends:

• Move unfinished issues forward to the next cycle or back to the backlog
• Review completed work against the cycle goal
• Start the next cycle according to team automations

Workspace admins may configure automations that roll open issues forward — check team cycle settings.

Analytics

Cycle and project graphs use estimates (or a default of 1 point per issue when estimates are off) for scope and completion percentages. See estimate analytics in Estimates.

Next