Release runs
Each release run has its own page. On the Pipeline view of the Tasks page open it from Run on a project's Release step, from Open run in a release row's ⋯ menu, or from a row of the folded Runs list under the last stage. On an incident's page, Jaah release and a suspect's Release # open it too. What a release is and how it gets recorded is in How Production QA works.
The page is part of Production QA: while your plan does not include it, the page shows Not on your plan with "Your plan doesn't include Production QA." Org admins also get See plans; anyone else reads Ask an admin to change the plan.
The page
It opens as a panel beside the Tasks board, headed by the project and environment with the run's status beside it: Queued, Releasing, Succeeded, Failed, Cancelled or Skipped. At the panel's top right, Maximize pane gives it the full width, Restore pane brings the board back, and Close pane closes it. On a phone it opens as a full page. It is read-only, refreshes every 15 seconds, and has three tabs.
Overview
- Project and Environment.
- Range: the commits it shipped, as
first..last: First recorded release when there is no earlier release to measure from, Rollback when it released a commit an earlier release already shipped, Pending while the range is still being worked out, and Partial when only part of it could be read, each with a note on why. - PRs: each pull request in the range. One with a task links to that task, followed by ledger Applied once the release is counted in the task's outcome, or Pending until it is (Revoked if it was withdrawn). With more than one repository, each shows its repository too.
- Other commits: commits in the range that no known pull request carries. Shown only when there are any.
- Failed at: the job and step the run reports as failing. Shown whenever the run reports one, even on a run that ended Succeeded.
- Run: the workflow and run number, linking to the run in your repository host, with the attempt when it ran more than once.
- Event: what started the run.
- Commit: the commit it released; hover for the full hash.
- Received, Started and Finished: when Jaah first heard of the run, and when it started and ended.
- Environments: when one run released to more than one environment, each environment with its state and job.
Metrics
What the regression window measured after a production release: one section each for Error rate and p95 latency, with Baseline (before the release), After, Change (marked Breached when it passed the project's limit), Window (minutes, and the events counted) and, when there is one, a Note. A metric with no data shows Result Not measured: and why.
With nothing measured the tab reads Pending — measured and a time while the window is still open (Pending alone before that time is known), or Not measured: and the reason, such as "not a production release" or "no monitor reports this project".
Probes
- Run: the task that ran the probes for this release, then its state while it has not reported, such as Running, or when it reported. It adds Skipped: Production QA off, Skipped: project not opted in or Skipped: a later release superseded it when nothing was probed.
- Results: each health URL and smoke command: Passed or Failed, its name, HTTP or Command, the status code or exit code and how long it took, and Incident # with its number when a failure filed one. Output opens what it printed.
- Incidents: the health incidents on this release: Failing or Passing, the code and time taken, the incident's state, and when it was last seen, which opens the incident.
With none of these the tab reads No probe results.
A release that is not there
A release that is gone, one no project has reported yet, or one in a project you cannot see opens as a full page, not a panel beside the board, on one line: Release not found. Releases appear here once the project reports them.

Related
- How Production QA works: releases, regressions and probes.
- Turn on Production QA for a project: connect releases and set the release workflows, regression limits and probes.
- Incidents: the incidents a release can lead to.