Cycles and releases

A cycle plans when work happens. A release records what shipped. This page covers both, and the pipeline that connects a finished item to a published version.

Cycles

A cycle is a time box for planning work — two weeks, for example. A cycle is not owned by one project. The same cycle can hold items from every project on the server.

Create a cycle

You need the cycle.update permission atom.

1. Open Settings → Cycles. Click New cycle.
2. Type a Name.
3. Set a Start date and an End date, or leave both blank to create a draft you schedule later.
4. Add an optional Goal.
5. Under Visible to, pick teams if the cycle should stay private to them. Leave it empty and every member sees the cycle.
6. Click Create cycle.

Turn on Recurring cycle to auto-provision future cycles under the same label. Give it a schedule — a starting weekday and a duration in days — or leave it unscheduled and provision dateless drafts instead.

Add work to a cycle

Open a work item. Find Cycle in the item panel. Select a cycle.

An item can belong to one cycle at a time. Its earlier cycles stay on record as its carry-over trail.

To move several items at once, select them in a view. Then choose Cycle… from the bulk-action bar.

Cycle states

Radd derives a cycle's state from its dates. You never set it directly, except by completing the cycle.

State	Meaning
Draft	No start date or end date yet — a staging area, never active
Upcoming	Scheduled, but today is before the start date
Active	Today falls inside the start and end dates
Completed	Today is after the end date, or someone completed the cycle early

Click Complete cycle on an active cycle to close it before its end date. Completing a cycle moves its open items to another cycle, or to the backlog. Radd can start that next cycle for you, and top up its recurring series, in the same step.

Only Settings → Cycles groups completed cycles for browsing. The sidebar's Cycles section, and the bulk Cycle… action, both drop a completed cycle from the list. The Cycle field on one item does not — it still offers every cycle, including completed ones.

Cycles in reports

A project's Reports page, and the server-wide Reports page, both chart cycles:

• Velocity — how much work (a count, or story points) entered the done category during each of the last several completed cycles.
• Burnup — for one cycle you choose, the work in scope each day against the work completed each day, over the cycle's window.

Burnup needs a scheduled cycle. A draft cycle, with no start and end date, has no window to plot.

Releases

A release is a version of one project's work, for example 0.4.0. An item can target a release through its Release field in the item panel.

Create a release

You need the release.update permission atom, scoped to the project.

1. Open the project's Settings → Releases. Click New release.
2. Type a Version (unique within the project) and a Name.
3. Add optional Description notes — what the release contains.
4. Click Create release.

A new release starts Planned. Click Mark released to set its status to Released. Radd stamps the release date the first time you do this, and keeps that date even if you later mark it Planned again.

Delete a release to remove the version. Items that targeted it keep their history. Only the release row goes. This cannot be undone.

The release pipeline

Waiting for release is a state, not a release. It means the work is finished but has not shipped. It belongs to the done category, so Radd's throughput counts the day the work was finished, not the day someone later cut a version.

Two project settings name the states the pipeline moves between, on Settings → Releases under Release pipeline:

Setting	What it does
Waiting-for-release state	The state that means "finished, not yet shipped"
Shipped state	Where the sweep moves an item once its release publishes

Leave either setting empty to turn that half of the pipeline off for the project.

Publishing a version sweeps the pipeline. The sweep moves every item sitting in the waiting state to the shipped state, and records the release on each one. The sweep is safe to run twice. An item already shipped stays untouched, so nothing repeats.

A sweep runs two ways:

• Automatically, when a connected Forgejo repository publishes a release (see Project settings for connecting one).
• By hand, through the API or the MCP sweep_release tool. A sweep needs no Forgejo connection at all.

Clicking Mark released does not sweep by itself. It only changes that release row's own status. Radd's settings pages carry no Sweep button — running one by hand needs API or MCP access, not the browser. If a webhook is missed, ask an administrator to run the sweep.

How an item gets a release

An item gets a release one of two ways:

• You set it. Open the item. Find Release in the item panel, and select a version.
• The sweep sets it. The item is sitting in the waiting state, and its project's release publishes.

Either way, the release then shows as a chip on the item, in views, and on cards.

---

Mirrored from project.radd-hq.com on 2026-09-12. Documentation is written there; this copy is regenerated by scripts/publish_wiki.py and hand edits do not survive it.