Cycles and burndown
Plan a project in time-boxed iterations — create a cycle, start it, track its burndown, and complete it.
A cycle is a time-boxed iteration of a project — a sprint, a week, a delivery window. Tasks assigned to a cycle roll up into a burndown so you can see whether the work is on track to finish inside the window.
Cycles live inside a project. Open a project and use the Cycles link
in the details rail to reach its cycles list at /pm/projects/{id}/cycles.
What you can do here
- Create a cycle — click New cycle, then give it a Name (e.g. Sprint 12), a Start date, an End date, and an optional Goal.
- Start a cycle — an upcoming cycle stays in planning until you click Start. Starting it moves it to Active.
- Track burndown — open a cycle to see its burndown chart and the tasks assigned to it.
- Complete a cycle — click Complete when the window closes, even if some tasks carry over.
Cycle states
- Upcoming — created but not started yet.
- Active — in flight. Only one cycle is the current working window.
- Completed — closed out.
The cycles list groups cycles under Active, Upcoming, and Completed headers so the current window is always at the top.
Reading the burndown
The cycle detail page shows a burndown chart for the cycle window. If the window has no working days yet, you'll see No burndown data — the cycle window is empty. Assign tasks to the cycle (and give the cycle real start and end dates) for the chart to populate.
Tips
- Set honest start and end dates. The burndown is only as good as the window you give it.
- Don't leave a finished cycle Active. Completing it is what lets the next cycle become the working window and keeps reporting clean.
- Carry-over is normal — complete the cycle and let unfinished tasks move to the next one rather than stretching the dates.
Permissions
Creating, starting, completing, and deleting cycles requires project edit permission. Anyone who can view the project can read its cycles and burndown.