Cycles
Time-boxed sprints with automatic status and progress tracking.
View as MarkdownCycles are time-boxed sprints for a team. Create one from the Cycles page — the dates default to two weeks — then add issues through each issue's Cycle property. Tasks computes the cycle's status from its dates and tracks progress as issues reach a completed status.
Start a cycle
- Open Cycles in the sidebar and choose New cycle.
- Optionally name it — unnamed cycles are numbered automatically (
Cycle 3). - Set Starts and Ends. The form suggests a two-week window starting today; any dates work.
- Choose Start cycle.
Put issues in the cycle
Set the Cycle property on an issue — from the New issue composer, the issue page, or the side panel. Sub-issues inherit their parent's cycle automatically, so breaking down a scheduled issue keeps the pieces in the sprint.
Reading the Cycles page
Each cycle row shows its dates, a status chip, and progress:
| Chip | Meaning |
|---|---|
| Upcoming | The start date is in the future |
| Active | Today is between the start and end dates |
| Completed | The end date has passed |
| Planned | Dates haven't been set |
Status comes straight from the dates — there's nothing to update by hand. Progress counts issues whose status is a completed one (canceled issues don't count as done).
Frequently asked questions
Can I edit a cycle after starting it?
Not yet — a cycle's name and dates are fixed at creation, so double-check the window before you start it. Issues can move in and out of a cycle at any time via their Cycle property.
Last updated on