Cycles

Cycles are named checkpoints that help teams organise and track progress — Sprints, Releases, Iterations, or any goal your process demands. Admins define reusable Cycle Types in the admin panel; project members create actual cycle instances from those types inside their projects.

How it works

Cycles follow a two-level model that separates setup from day-to-day use:

Level Where What it defines Example
Cycle Type Admin → Cycles The category template — name, icon, color, and which projects can use it Sprint, Release, Iteration
Cycle Inside a project A concrete instance of a type — with its own name, dates, status, and progress Sprint 42, v2.1 Release

Admins configure Cycle Types once. Project members then create cycles from those types without needing admin access.

Getting started (admin)

  1. Go to Admin → Cycles.
  2. Click Add Cycle Type and define a name, icon, and icon color.
  3. Choose which projects the type should be available in — all projects or a specific subset.
  4. Optionally mark one type as the workspace default — it will be pre-selected when project members create a new cycle.

Getting started (project members)

Once an admin has created at least one Cycle Type, project members can start using cycles:

  1. Open your project and click Cycles in the sidebar.
  2. Click New Cycle and fill in a name, type, optional dates, and an optional parent cycle.
  3. Start the cycle when work begins — this locks the start date and moves it to Active.
  4. Track progress on the detail page using the Results, Status, Activity, and Issues tabs.
  5. Complete the cycle when the work is done.

Who can manage cycles?

Action Who can access
Create, edit, or delete cycle types (admin) Tenant Admin, Project Admin
Set the default cycle type (admin) Tenant Admin, Project Admin
View cycles in a project Users with View cycles permission
Create, edit, delete, start, complete, or reopen cycles in a project Users with Manage cycles permission