BriefFlow

Search documentation

Search BriefFlow's documentation by page title, section heading, or content.

What this does

A release is a named, versioned delivery scoped to one project — "Mobile Application 2.4.0" and "Customer Portal 2.4.0" are two separate releases, not the same version number colliding. BriefFlow tracks release readiness; it doesn't perform deployment automation. Marking a release Released is a record of delivery, not a trigger that deploys anything.

Before you begin

Creating or managing a release requires the releases.manage permission (Administrators by default).

Creating a release

Administrator permission required

Requires the releases.manage permission.
  1. Open Releases in the sidebar.
  2. Select Create Release.
  3. Choose the Project this release belongs to.
  4. Enter a Version (e.g. 2.4.0).
  5. Optionally add a name, description, and planned release date.
  6. Submit.
The Releases list — progress and readiness across every project.

Assigning tasks to a release

A task can be linked to a release from the task's own edit form — set its Release field to the release you want it in. A task marked as requiring a release (the default) can't reach Done without one.

Release status

  1. Open the release's detail page.
  2. Use the status control to move it through Planned → In Development → QA → Released (or Cancelled).

These statuses track the release as a whole — separately from the status of any individual task linked to it.

What happens next

The release's detail page shows how many of its linked tasks are Done versus still in progress, blocked, in QA, or ready for release — a simple, honest completion count, not a weighted or estimated percentage.

A release's detail page — linked tasks, progress, and participants.

QA and release readiness

Important

A release can be marked Released only once every task linked to it is Done — which itself required each of those tasks to have passed QA if QA was required for them. This keeps "Released" meaning what it says: everything in it actually shipped, tested.

Common issues

I can't mark a release as Released. One or more linked tasks aren't Done yet. Open the release detail page to see which ones are still outstanding.

The task I want to link doesn't show a matching release. Releases are project-scoped — the release must belong to the same project as the task.

Related guides