Releases & Approvals
A release is ready when the testing behind it is done and signed off. Releases & Approvals links your test plans to release cycles so readiness is visible, and it puts approval gates in the path so nothing advances before a lead says so.
Who it’s for#
Release managers and QA leads who decide when work moves forward and need a clear gate to control it.
What it does#
- Plan to release linkage — connect test plans to release cycles to see whether a release is tested and ready.
- Promotion workflows — move work forward through environments as it qualifies.
- Approval gates — require sign-off on test plans and critical paths before they advance.
- Rule-based routing — send each approval to the right reviewer automatically.
- Bulk actions — clear or approve many items at once when the picture is clear.
- Impact analysis — see how code changes affect coverage so you know what to re-test.
How it works#
Your test plans report up to the release they support, so readiness is never a separate spreadsheet. Approval gates with rule-based routing put the decision in front of the right person, and impact analysis flags the tests a change touches before you promote.
Why it matters#
Promoting an untested release is how regressions reach users. Tying plans to releases and gating promotion on real sign-off keeps that decision deliberate instead of accidental.