This guide covers the build-specific features of releases. For a complete overview of releases, including readiness verdicts, thresholds, and metrics, see Managing Releases & Release Readiness Dashboard in the help documentation.
Setting a Version Pattern on a Release
When you create or edit a release, you see a Version Pattern field (visible only when Builds are enabled).
What It Does
A version pattern is a glob-style wildcard that matches build versions. Any build version matching the pattern automatically belongs to that release.
Example
Release name: "Release 2.14" Version pattern: 2.14.*
Result: Any build with a version like 2.14.0, 2.14.1, 2.14.5, or v2.14.0 automatically links to Release 2.14. Builds with versions 2.15.0 or v3.0.0 do not match.
Setting the Pattern
Go to Releases > Releases
Click New Release or edit an existing release
Fill in the release name, description, and other fields
Scroll to the Version Pattern field
Enter a pattern like
2.14.*or leave it blank if you don't want automatic matchingClick Save
From that point on, new builds matching the pattern automatically attach to this release. See "Grouping Builds Under a Release" for more details on how patterns work.
Viewing Builds in a Release
The Release Readiness page shows the full status of a release, including all builds it contains under the Test Plan Breakdown table.
Accessing Release Readiness
Go to Releases > Releases
Click the release name to open its detail page
Build Column in the Test Plans Table
On the Release Readiness page, the Test Plans table has a new Build column (visible only if test plans in this release are linked to builds).
This allows you to quickly see which test plans are tied to which builds within a release.
You see these relationships at a glance in the test plans table.
Why This Matters
Grouping builds under releases and linking test plans to specific builds gives you clear traceability:
Release 2.14 overview - see all software versions (builds) and their testing results
Plan-to-build mapping - know exactly which test plan ran against which version
Full audit trail - from release down to specific test results for a specific build
This is especially important for regulated industries where you need to prove that every version going to production was properly tested.
Related Articles
The Build Detail Page - Learn about all the coverage and traceability metrics available for a single build
Managing Releases & Release Readiness Dashboard - Complete guide to release readiness, thresholds, verdicts, and comparison views
Grouping Builds Under a Release - Detailed guide on version patterns and automatic build linking