A release is a named, versioned delivery scoped to one project — "TimelinxMobile 3.9.5" and "Presence 3.9.5" are two separate releases, not the same version number colliding.

Creating a release#

Creating a release (requires releases.manage) captures a project, a version, an optional name and description, and an optional planned release date.

Release status#

A release moves 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.

Assigning tasks to a release#

A task can be linked to a release from the task's own edit form. A task marked as requiring a release (the default) can't reach Done without one.

Release progress#

A 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.

QA and release readiness#

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.

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.