Cycles

Plan time-boxed iterations with burndown tracking.

Creating a Cycle

Navigate to Cycles in the sidebar and click New Cycle. Provide a name, start date, and end date. Cycles belong to a team — select the team from the dropdown.

Cycle Status

A cycle's status follows its dates:

• Upcoming — start date is in the future
• Active — from the start date until the end date
• Completed — from the end date on

Velocity moves cycles along automatically once an hour. Dates are UTC calendar days, and a cycle ends at the start of its end date: a cycle from 2026-09-22 to 2026-10-06 is active through October 5 and completed on October 6 (UTC). Each move sends a cycle.started or cycle.completed event to your webhooks and to Zapier's Cycle Started and Cycle Completed triggers.

Changing a cycle's dates moves it back at once if needed: extending a completed cycle makes it active again, silently. Moving forward is left to the hourly check, and only a start or end date of today or yesterday sends an event. A cycle whose dates are further in the past moves along without one.

Adding Issues

Add issues to a cycle from the issue detail panel by setting the Cycle field, or from the cycle detail page. Issues in a cycle are tracked toward the cycle's completion goal.

Burndown Chart

Each cycle has a burndown chart showing:

• Remaining (blue) — issues not yet completed
• Ideal (dashed) — linear progress from total to zero
• Completed (green) — issues done so far

Velocity captures daily snapshots recording totalIssues,completedIssues, totalPoints, and completedPoints. The burndown chart is generated from these snapshots.

Progress Tracking

The cycle detail page shows a progress bar and stat cards for total, completed, and in-progress issue counts. The issues list below shows all issues in the cycle with their current status.