Skip to main content

Release Visibility

Use Release Visibility to review a Jira release with automated runs, manual cycle outcomes, and BDD behavior mapping in view.

This view extends basic release linking by showing which runs belong to a release, which behaviors are mapped, and which work items still lack evidence.

Release visibility board showing linked cycles, readiness callout, evidence mix, and issue coverage for a selected Jira release

What Release Visibility Shows​

For a selected Jira release, Testream can show:

  • Linked test cycles
  • Cycle pass rate and execution summary
  • Behavior evidence coverage percentage
  • Evidence mix across automation and manual execution
  • Issue coverage buckets that show mapping gaps
  • A release-review callout

Linked Cycles​

When a release has linked test cycles, the Releases page shows:

  • Cycle name
  • Cycle state
  • Last updated time
  • Pass rate
  • A compact execution summary
  • A direct Open cycle action

This helps release owners move from aggregate status into the exact cycle that still needs work.

Release Review Callout​

Testream summarizes the selected release with a state that points to the next review action.

ReadinessMeaning
No scopeThe release has no Jira issues yet
Needs mappingThe release issues are not yet mapped to BDD behaviors
Action neededFailed or blocked evidence is present
Needs evidenceBehaviors are mapped, but some still have no evidence
ReadyMapped behaviors have evidence and no failed or blocked results remain

Use this state as review support, not as a replacement for release judgment.

What counts toward the state​

Testream reads a release through its Jira issues: each issue's mapped behaviors, and the evidence for those behaviors.

  • Automated evidence counts when the behavior is mapped to an issue in the release, the automation link is confirmed, and the test run is linked to the release.
  • Manual evidence counts when the behavior is mapped to an issue in the release and the result was recorded in a test cycle linked to the release.
  • Failed or blocked results in a linked cycle always count. If a cycle linked to the release has a failed or blocked result, the release shows Action needed, even when that behavior is not mapped to an issue in the release. A passed result on a behavior that is not mapped to a release issue does not move the release toward Ready, because it does not show that a release issue is covered.
  • Skipped is not evidence. A behavior whose latest manual result is skipped is treated as having no evidence yet.
  • Archiving a cycle clears its unmapped failures. A failed or blocked result on a behavior that is not mapped to a release issue stops counting once its cycle is archived. Results for behaviors mapped to a release issue still count after archiving, so archiving a finished cycle does not remove evidence.

When a behavior has several manual results in the release's cycles, the latest one is used.

Evidence Coverage and Evidence Mix​

The release board shows how much of the mapped behavior set already has evidence. The percentage covers behaviors mapped to the release's Jira issues. Results on behaviors that are only in a linked cycle do not change it.

Evidence can come from:

  • Automation linked to the release
  • Manual pass results
  • Manual fail results
  • Blocked manual results
  • Behaviors that still have no evidence, including behaviors whose latest manual result is skipped

This helps teams distinguish between:

  • A release that has broad coverage
  • A release that is only partially evidenced
  • A release that still needs mapping work before execution can even begin

Issue Coverage Buckets​

Release Visibility also groups release issues into three buckets:

BucketMeaning
Issues with evidenceAt least one mapped behavior already has manual or automation evidence. A skipped result is not evidence
Mapped issues without evidenceBehaviors exist, but none has evidence yet
Unmapped release issuesNo BDD behaviors are linked yet

This is especially useful for finding release items that look in scope from Jira planning, but still have no usable test behavior map.

Issue coverage section with buttons for issues with evidence, mapped issues without evidence, and unmapped release issues

Issue coverage buckets on the release board. Use these buttons to separate release issues that already have evidence, are mapped but still unevidenced, or are still unmapped.

Issue coverage details modal listing Jira issues in the selected release coverage bucket

Issue coverage details modal after selecting a bucket. Use this view to inspect the exact Jira issues behind each release coverage gap.

How It Connects To Test Run Details​

If a test run is linked to a release, Test Run Details also shows:

  • The linked release
  • The release issue, when present
  • Linked test cycles for that release
  • A direct path to the release board

That means teams can move in both directions:

  • From a release into a cycle
  • From a run into the release board
  • From a release-linked run into the specific cycle that still needs execution

Best Practices​

  • Link runs to releases as soon as they become relevant to a shipping version.
  • Map release issues to reusable BDD Library behaviors early, not at the end.
  • Use cycles for manual evidence that automation does not cover yet.
  • Treat unmapped issues as a visibility gap, not just a documentation gap.
  • Review blocked and failed manual evidence before treating a release as ready.
  • Map the behaviors in a release's cycles to the release issues they verify, so passed results count toward coverage.

Next Steps​