Time-box your work. Ship with confidence.

Cycles are time-bound containers for your team's work. Commit to a goal, pull in a set of issues, and watch built-in burndown and velocity tracking do the rest.

Active, upcoming, and completed cycles in one view.

Sprint 5Active

Jun 3 – Jun 1718 / 29 issues

Ship the auth refactor and stabilize the analytics dashboard.

62%

Sprint 6Upcoming

Jun 18 – Jul 20 / 22 issues

Cycle planning meeting scheduled for Jun 17.

Sprint 4Completed

May 20 – Jun 331 / 31 issues

Closed on schedule. Two issues rolled to Sprint 5.

100%

Sprint 3Completed

May 6 – May 2026 / 28 issues

Closed with two unplanned issues from production.

100%

How cycles work

From planning a cycle to closing one cleanly.

Four building blocks. Together they cover the full sprint lifecycle, from the first idea on the backlog to the final retro.

01 · What is a cycle?

A goal, a date range, and a committed set of issues.

A cycle has a start date, an end date, and a list of issues the team agrees to ship inside that window. Past cycles stay searchable, the active cycle drives every dashboard, and the upcoming cycle gives the team time to plan.

Start date, end date, and a goal statement
Past, active, and upcoming states
Searchable history of every closed cycle
Friendly to teams new to agile

Completed Active Upcoming

Sprint 3Completed

May 6 – May 20

Sprint 4Completed

May 20 – Jun 3

Sprint 5Active

Jun 3 – Jun 17

Sprint 6Upcoming

Jun 18 – Jul 2

Past

Closed cycles stay searchable. Their backlog rollovers, scope changes, and velocity feed every analytic view.

Active

The team is working inside a time-boxed window. Progress, burndown, and scope changes update as work moves.

Upcoming

The next cycle gets planned from the backlog. Commit to a goal and a set of issues before kickoff.

02 · Create and manage

Spin up a cycle in under a minute.

Give the cycle a name, set the date range, write a one-line goal, and pull issues straight from the backlog. Drag to reorder, filter to focus, or use a template to start from a known-good cycle shape.

Name, date range, and a goal statement
Drag-and-drop issues from the backlog
Filter the backlog by label, priority, or assignee
Status pipeline: Draft, Active, Completed

03 · Progress and analytics

Burndown, velocity, and scope at a glance.

The burndown chart shows ideal versus actual progress over the cycle window. Velocity trends across recent cycles so planning gets sharper every time. A completion ring sits on every cycle card, and scope-change alerts surface the moment work gets added or removed.

Ideal vs actual burndown chart
Velocity trended over recent cycles
Completion ring on every cycle card
Scope change alerts in real time

Burndown

Ideal Actual

10 days29 → 0 issues

Completion

18 of 29 issues done

Velocity

issues per cycle

Sprint 1

Sprint 2

Sprint 3

Sprint 4

Sprint 5

Scope changes

+3 issues added after kickoff

Auth refactor scope grew on day 4.

−1 issue moved to next cycle

Doc cleanup deferred to Sprint 6.

04 · Handling incomplete issues

Close out a cycle without losing context.

When a cycle ends, the transfer screen lists every incomplete issue with its assignee and priority. Roll work into the next cycle in one click, or send it back to the backlog if priorities have shifted. Nothing falls through the cracks.

One-click rollover to the next cycle
Per-issue choice: next cycle or backlog
Summary of what is moving and what is closing
Scope changes captured in the cycle history

Run your first cycle in under a minute.

Start with a cycle template, pull in a goal, and ship with the confidence of a built-in burndown and velocity view.

No credit card required