Skip to main content
A cycle is a time box, often one or two weeks, with a set of work items the team commits to. Collabase calls sprints Cycles. You plan a cycle in the Backlog, run it on the Board, and review it in the Cycles tab.

Switch cycles on

Cycles are a project feature. A project admin switches them on under Settings → Project features → Planning & tracking → Cycles. Projects created from the Scrum template have them on. The Cycles tab is visible to members whose role can create, start, complete, edit or delete cycles.

Cycle lifecycle

The Cycles tab groups them in Active, Upcoming and Completed.

Create a cycle

1

Open the dialog

Click Add Cycle in the Cycles tab, or Create Cycle in the Backlog.
2

Fill in the cycle

Enter a Name and, optionally, a Cycle Goal. Start Date defaults to today, Due Date to today plus the project’s Default cycle duration.
3

Create it

Confirm, or press Cmd + Enter (Mac) or Ctrl + Enter (Windows and Linux). The cycle appears under Upcoming with the status Planned.
Change a cycle later with Edit Cycle in its actions menu.

Start a cycle

Open the actions menu of a planned cycle and choose Start Cycle. The cycle starts at once, without a confirmation. Collabase records the committed story points at that moment, so work added later shows as scope change.
If another cycle is already active, the start does not happen and Collabase shows Cycle not started with the reason. Complete the active cycle first.

Follow a running cycle

Expand the active cycle to see its charts. The burndown uses the estimates of the work items. When nothing is estimated, it counts work items instead. On the Board, the Scope menu shows only the active cycle’s work items by default.

Complete a cycle

1

Choose Complete Cycle

Open the actions menu of the active cycle and choose Complete Cycle. The dialog shows how many work items are done.
2

Decide where unfinished work goes

Under Move unfinished work items to, choose Move to Backlog (the default) or a planned cycle.
3

Confirm

The cycle moves to Completed and the unfinished work items move as chosen.

Review completed cycles

Use the velocity chart to size the next cycle. If the team completes about 30 points per cycle, a cycle planned at 50 points will likely carry work over.

Estimation

When Story Points is switched on under Project features, Settings → Estimation offers one Estimation Method for the whole project:
The committed value recorded at the start of a cycle counts story points only. With T-shirt sizes or hours, the burndown and velocity fall back to counting work items for the committed side.

Subtasks and cycles

Two settings under Settings → Cycles keep parents and children together when they move between the backlog and cycles: Both reach one level only. The same section holds Default cycle duration and Allowed work item types.

Who can manage cycles

Each action has its own permission in the Space’s Permission Scheme: Create cycle, Start cycle, Complete cycle, Edit cycle, Delete cycle and Manage cycle scope (moving work in and out).
Delete Cycle runs without a confirmation.

Next steps

Backlog

Rank work and plan it into cycles.

Project reports

All charts and reports in one place.
Last modified on October 23, 2026