Releases configuration

The Releases admin area is the organization-wide view of release activity. Where the Releases section covers planning and approving a release within a project, this is the administrator’s vantage point across every project at once.

The organization-wide lens exists because release risk is often a portfolio problem, not a project one. A quality lead needs to see, in a single view, which releases are approaching their gates, which are stalled awaiting sign-off, and which are shipping this cycle — questions that are invisible when release state is locked inside each project. This consolidated view is where someone accountable for the whole program catches a release that’s slipping before it becomes a missed commitment.

Releases across all projects

From here you can see releases spanning all projects, rather than working inside one project at a time. For someone responsible for the organization’s overall release cadence — a quality or program lead tracking what’s shipping where — this consolidated view answers “what’s in flight across everything?” without hopping between projects.

Administrative oversight

The admin view supports the housekeeping that sits above individual release work: reviewing the full set of releases and managing them at the organization level. This keeps the release record tidy across a large portfolio, complementing the in-project workflow rather than replacing it.

Where releases are actually worked

The substance of a release — bundling its scope, tracking readiness gates, and approving it with an electronic signature — happens within the project, as described in Planning a release and Approving a release. This area is the organization-level lens over all of that.