Releases

A Release in the PM module is a named, versioned bundle of features that will ship together, for example v2.3 - Payments refresh or 2026.04 - Onboarding polish. Releases give you a target date to work toward and a visible scope that stakeholders can point at.

URL: /pm/releases
Required permission: pm.view (create / edit / delete require pm.create, pm.edit, pm.delete)

The Release List

/pm/releases shows every release across every product in one paginated table (25 per page), ordered by target date, newest first. Each row shows:

You can filter by product in the top-right dropdown. There is no text search on this page; use /pm/releases?status={status} directly if you want to filter by lifecycle state.

Creating a Release

1. Click New Release on /pm/releases.

2. Fill the form:

   • Product (required): which product this release ships under.

   • Release Name (required, max 100 characters): e.g. v2.3 or 2026-Q2.

   • Description: release notes, changelog highlights, anything you want stakeholders to see on the detail page.

   • Status: defaults to planning.

   • Target Date: when you expect to ship.

3. Click Create Release.

Release Lifecycle

A release progresses through five statuses:

Status is a dropdown on the edit form. It does not transition automatically. Move it forward manually as you go.

Assigning Features to a Release

Features target a release, not the other way round. To put a feature into a release:

1. Open the feature (from the Backlog or the Roadmap).

2. Click Edit.

3. Under Linked Items, pick the release from the Target Release dropdown.

4. Save.

Once saved, the feature appears in the release's Features table on the release detail page. You can also set target_release_id when you first create the feature.

To remove a feature from a release, edit the feature and set Target Release back to "None". There is no bulk-add UI inside the release detail page; all assignment happens from the feature side.

The Release Detail Page

/pm/releases/{id} shows:

• Release name, status badge, target date, and released_at date if set.

• An optional Completion progress bar (shipped features / total in the release, as a percentage).

• The release description (rendered with line breaks preserved).

• A Features table listing every feature whose target_release_id points at this release, with status and RICE score. Click any feature to open it.

Ship Notes and Changelogs

The release description field is your changelog. There is no separate "release notes" editor and no automatic changelog generation from feature names today; you write the description manually on the release create / edit form. It supports multi-line text and is rendered with line breaks intact on the detail page.

If you need rich formatting or a public-facing changelog, publish it in the Docs module and link from the release description.

Cross-Link to Engineering Work

Releases in PM are the "what ships" layer. The engineering work for shipping them lives in the Projects module: each feature can spawn a linked project (see the Dev Handoff section of Backlog). A typical flow:

1. Create a release in PM with a target date.

2. Assign planned features to the release.

3. For each feature, click Create Project on its detail page. This creates a Projects-module project and flips the feature to in_development.

4. Engineering runs the project (tasks, time tracking, milestones) under the Projects module. See Projects overview.

5. When each feature ships, mark it shipped. The release progress bar updates.

6. When every feature is shipped, move the release itself to released.

Deleting a Release

Click Edit, scroll down, and delete from the release's detail page (requires pm.delete). Deleting a release does not delete its features; they remain in the backlog with target_release_id cleared.

Related Documentation

• Backlog and RICE: feature prioritisation and dev handoff.

• Roadmap: the product-level visual plan.

• PM Overview: how releases fit the entity model.

• Projects overview: engineering execution layer.