---
title: Cycles
summary: How to plan a project's work in cycles, follow a cycle's progress and complete it.
---

A cycle is a stretch of time in one project, with the issues planned for it. An issue is in at most one cycle. A project's cycles never overlap. Each cycle has a number in its project, shown as `C12`, a name, an optional description, a lead and its dates. Every member can create, change and complete cycles.

## The Cycles page

Open a project's **Cycles** tab in its header, or press `g` `c`. The header's tab shows the cycle in progress and the days it has left.

- The cycle in progress is on top: its progress by state, a burn-up chart, the reviews in it that wait on you, and its assignees.
- Below are **Upcoming**, **Drafts** and **Completed**. Each row opens that cycle's page.
- A cycle past its last day that is not completed yet asks to be completed.

## Create a cycle

Press **New cycle**. Give it a name and, if you like, a description and a **Lead**. Pick the dates on the two-month calendar, where the project's other cycles show as bars; **Length** sets 1 to 4 weeks from the start. Dates that overlap another cycle show in red, with the first free start.

Without dates, the cycle is saved as a draft (**Save draft**): plan issues into it, and pick dates later.

Edit an upcoming or draft cycle from its row's menu (**Edit…**), or any unfinished cycle from **Edit cycle** on its page. Once a cycle has started, its start date is fixed. The row's menu also has **Delete**: its issues leave it. A completed cycle cannot be deleted.

## Put issues in a cycle

- Set an issue's **Cycle** property. The picker offers the active, upcoming and draft cycles, and none; completed cycles are not offered.
- Create an issue from the cycle's page: it joins that cycle.
- In the new issue panel, set its cycle chip.

## A cycle's page

A cycle's page shows its issues as a list or a board, grouped in workflow order. **Details** opens a panel with progress, the burn-up, assignees and the cycle's details.

The burn-up chart draws, for each day of the cycle, the issues done, the ones started and not done, the whole scope, and the ideal line. Hover it for a day's numbers.

## Complete a cycle

Press **Complete** on the cycle's page. The dialog shows the cycle's numbers and its unfinished issues. Under "Move the unfinished issues to", pick:

- **Next cycle**;
- **Another upcoming cycle**;
- **No cycle**: back to the project, outside any cycle.

Untick an issue to leave it in the completed cycle. Done issues stay in the cycle as its record. Press **Complete and move N**.

A completed cycle is read-only. Its numbers are frozen, and its page lists the issues it moved on and where they went.

## Automatic rollover

Project settings › Cycles › **Automatic rollover**, off by default. When it is on, after a cycle's last day (UTC) the cycle completes itself, and its open issues move to the next cycle; done and cancelled ones stay as its record. If there is no next cycle, they wait in the ended cycle until there is one.

When it is off, open issues stay in an ended cycle until someone completes it.

## Find issues by cycle

In a list's query, `cycle:` takes a cycle's name, its number (`cycle:C12`), `active`, `next` or `none`. A list can also be grouped by cycle. See [Query language](/docs/finding/query).

## From the terminal

```sh
rsva cycles -p ENG                          # the project's cycles in time order
rsva cycle show C12 -p ENG                  # a cycle and its issues
rsva cycle create "Sprint 4" -p ENG --start 2026-11-16 --end 2026-11-29
rsva cycle complete C12 -p ENG --move-to next
rsva cycle delete C13 -p ENG
```

`-p` names the project; without it, `rsva` reads `RSVA_PROJECT`. A cycle created without dates is a draft. `complete` needs `--move-to` with a cycle, `next` or `none`; `--keep KEY` leaves an issue in the completed cycle. See [rsva](/docs/terminal/cli).
