Skip to main content
A release is the planning container for a sprint, version, or cycle of testing. It captures scope, dates, branch, environment, build target, and testers, then rolls up progress across every linked run and session. Releases page showing active releases with status, runs, sessions, and timeline

​
Create Or Edit Release

Click Create Release on the Releases page to open the release form. The same form is used for editing: open a release, click … in the header, then Edit. Create Release dialog showing name, description, type, parent, dates, branch, environment, build target, testers, linked issues, and note fields

​
Release Scope

From a release’s detail page, you can add 3 items: a test run, an exploratory session, or a sub-release. Release detail page showing options to add a test run, exploratory session, or sub-release
  • Test run - Creates a manual run under this release. Good for a fixed list of test cases, like a smoke check before a deploy or a regression pass.
  • Exploratory session - Creates a session under this release. Best for unscripted testing where you set a mission, explore, and log findings as you go.
  • Sub-release - Creates a child release inside this one. Useful when a long cycle needs to split into phases, like a major version broken into a beta phase and a final phase (v2.0 → Beta → Final).
Note
  • Items added from the detail page link automatically to the release.
  • Sub-releases support up to 3 levels.

​
Track Progress on Release Detail

The detail page shows the release status, dates, edit options, and action buttons. Use the Results tab to track test progress and the Activity tab to see its runs and sessions.

​
Release States

Releases move through Not Started, In Progress, and Completed. Past Due appears if the due date passes before completion. Use Start, Complete, or Reopen to update the release state. Linked runs and sessions must be closed separately.

​
Results Tab

The Results tab combines test case results from every run in this release and its sub-releases. Session findings are counted in their own breakdown. A test case that appears in more than 1 run counts once, using its most recently updated entry. Adding a case to a new run shows it as Untested until someone records a result. A case a tester passed by hand and CI later failed counts as failed, the same way it reads inside the run. Automated results reach a release through its runs. Pick the CI run on the run itself, under Read automated results from. A release is only as accurate as the links behind its automated cases. A wrong or broken link reports the wrong result in the run, and the release rolls that number up without questioning it. See Keeping links accurate. Release detail Results tab showing test status breakdown, progress, note, and sub release sections

​
Activity Tab

The Activity tab lists the release’s runs and sessions, newest first, with each one’s status and who created it. Release detail Activity tab showing contributors and recent activity across linked runs and sessions

​
Release Type Settings

Use Type to categorize releases. You can also customize and manage these values via Test Case Settings → Test Execution → Releases → Release Type in the header. Settings page showing Releases tab with Release Type options

Runs

Track manual and automated cases inside a release

Sessions

Track exploratory work linked to a release
Last modified on September 29, 2026