Release Panel

Track a rollout for a Project through a sequence of stages, from planning to release.

What is the Release Panel?

The Release Panel tracks a Project's rollout through a sequence of stages — for example Requirement Review → Development → QA Testing — each with its own SLA, owner, and completion tracking.

Why use the Release Panel?

It answers “is this release actually ready, and who's holding it up right now?” at a glance, instead of chasing updates across chat threads.

When would I use this screen?

Planning a new version rollout for a project
Checking which stage a release is currently stuck at
Marking a stage complete so the release advances to the next one
Reviewing SLA compliance across all releases

Before you start

A release belongs to exactly one Project, and the Project can't be changed after the release is created (version numbering depends on it), so make sure you pick the right one up front.

Reading the stats

Stat	Meaning
Total Releases	Every release on record.
Active	Releases currently in progress.
Overdue / Blocked	Releases past their target date or stuck.
Delayed	Releases running behind schedule.
Released	Releases that have fully completed all stages.
SLA Compliance	The percentage of releases that met their stage SLAs.

How to create a release

Click New Release
Click + New Release at the top of the Release Panel.
Fill in Release Details
Choose the Project, a Target Date, and a Release Type (Patch, Minor, Major, Hotfix, Security or Bug Fix) — the version number is suggested automatically based on the type you pick. Also set Priority, Environment (Test / Staging / Production), a Status Tag, and any Change Type Tags that apply.
Switch to Pipeline Stages
Review the default stage pipeline (e.g. Requirement Review, Development, QA Testing). Each stage needs an SLA period, an Assign Type (Person or Group), and — this part is required — either a Person or a Group Name plus a Stage Leader.
Add or remove stages
Use + Add Stage to add another stage, or the trash icon to remove one.
Create the release
Click Create Release. Make sure every stage's required fields are filled in first — see Common problems below.

Advancing through stages

Open a release and use the Confirm stage done toggle on the current stage to mark it complete. ETA will automatically:

Advance the release to the next stage
Reassign the Current Owner to that next stage's leader
Recalculate the SLA countdown for the new stage
Record whether the completed stage finished early, on time, or late

Editing a release

Use Edit on a release's detail page to update its details. The Project field is locked once a release exists, since the version numbering depends on it — everything else remains editable.

Example

Release

EnOpSy Testing v0.0.1

Type

Patch

Environment

Test

Current stage

Stage 2: Development

SLA status

On Track

Video walkthrough

►

Video tutorial coming soon

Running a release through its pipeline

Creating a release, filling in each stage, and advancing it to completion.

Coming soon

Show transcript

Transcript will be added when the video is published.

Common problems

Problem

I filled in the release details but clicking Create Release does nothing.

How to fix it

Check the Pipeline Stages tab — every stage needs a Group Name (or Person) and a Stage Leader filled in. Right now, a stage missing either of those will silently block creation without pointing out which stage or field is the problem.

Problem

I can't find a way to delete a release.

How to fix it

There's currently no delete or archive option for releases in the UI. If you created one by mistake, contact your organization's administrator rather than trying to remove it yourself.

Problem

The Project field is greyed out when I try to edit.

How to fix it

This is expected — the Project a release belongs to can't be changed after creation, since version numbering depends on it.