Release Risk Analysis Skill
The Release Risk Analysis skill assesses release readiness from Zephyr Agent for Rovo. For a given release identifier, it examines every work item linked to the release, checks the test execution status of linked test cases and test cycles, and factors in any open bugs. It then returns a risk assessment for the release and for each high-risk story.
Use this skill when you need a data-backed answer to the question: "Is this release safe to ship?"
What it analyzes
For each work item linked to the release, the skill checks the following:
Whether the story has any linked test cases.
The latest execution status of those test cases across all cycles.
Whether any open bugs are linked to the work item or to its test executions.
The skill then rolls these results into a release-level risk summary.
Run a release risk analysis
To run a release risk analysis, do the following:
In Rovo, ask the Zephyr Agent for release risk. For example:
"Analyze release risk for FIX-2.4"
"What's the release risk for the release named 'Sprint 14 GA'?"
Confirm whether your project uses standard or custom execution statuses.
Standard statuses (Pass, Fail, Blocked, In Progress): No action needed. The skill proceeds to analysis.
Custom statuses: Provide a mapping to the standard categories in the following format:
pass: Done, Completed fail: Error, Failed blocked: Skipped, On Hold in progress: In Review, Running
If you leave any statuses unmapped, the skill flags them as Neutral and calls this out in the results. You can refine the mapping and re-run the analysis for full accuracy.
How risk is calculated
Story-level risk
Risk level | Criteria |
|---|---|
High | No linked test cases, or the latest execution is Fail, Blocked, or In Progress, or one or more open bugs are linked to the story or its test executions. |
Medium | Has test coverage but only Neutral (unmapped) execution statuses, or has linked test cases with no executions yet. |
Low | Has test coverage, all latest executions are Pass, and no open bugs are linked. |
Release-level risk
Overall risk | Trigger conditions |
|---|---|
High | High-risk stories make up 20% or more of total stories, or untested stories make up 20% or more. |
Medium | High-risk stories make up 5 to 20% of total stories, untested stories make up 5 to 20%, or any open linked bugs fall below the High threshold. |
Low | High-risk stories make up less than 5% of total stories, untested stories make up less than 5%, and no open linked bugs exist. |
What the output includes
Each analysis returns the following:
Overall release risk: High, Medium, or Low.
Risk summary: Total stories, high-risk count and percentage, untested story count, and open linked bug count.
Execution status summary: Grouped by project, showing counts per status, including custom statuses where applicable.
High-risk stories: A list of high-risk stories with the specific reason for each, such as a failed execution, missing coverage, or open bugs, linked directly to the relevant issues.
Recommendation: A short summary of what to address before shipping.
Important notes
Latest Executions wins
If a story has multiple test executions across different cycles, only the most recent execution counts toward its risk status.
Custom mapping applies per session
If your project uses non-standard statuses, provide the mapping each time you run the analysis, or keep a copy to paste in when needed.
Neutral statuses reduce confidence
If any statuses go unmapped, the skill calls this out rather than guessing. Risk for affected stories is classified as Medium at most, not High or Low.
Output focuses on high-risk stories only
The output does not include a complete inventory of all linked work items. It shows only the stories that are relevant to risk.