Validate proposed release blockers using Red Hat OpenShift release blocker criteria
Validates proposed release blockers using Red Hat OpenShift release blocker criteria.
/plugin marketplace add openshift-eng/ai-helpers/plugin install jira@ai-helpers[target-version] [component-filter] [--bug issue-key]jira:validate-blockers
/jira:validate-blockers [target-version] [component-filter] [--bug issue-key]
Note: target-version is required unless --bug is provided.
The jira:validate-blockers command helps release managers make data-driven decisions on proposed release blockers. It analyzes bugs with "Release Blocker = Proposed" status using Red Hat OpenShift release blocker criteria and provides clear APPROVE/REJECT/DISCUSS recommendations with detailed justification.
This command is essential for:
For detailed implementation guidance including JQL queries, scoring algorithms, and decision logic, see the jira-validate-blockers skill.
Parse Arguments and Build Filters – Extract arguments (target version, component filter, bug ID). Build JQL query for:
Query Proposed Blockers – Use MCP tools to fetch bugs based on mode:
Analyze Each Blocker – Apply Red Hat OpenShift release blocker criteria:
Generate Recommendations – Create report with APPROVE/REJECT/DISCUSS verdicts and justifications.
The skill file provides complete details on:
/jira:validate-blockers 4.21
/jira:validate-blockers 4.21 "Hypershift"
/jira:validate-blockers --bug OCPBUGS-36846
The command outputs a blocker validation report:
# 🚫 Release Blocker Validation Report
**Components**: All | **Project**: OCPBUGS | **Proposed Blockers**: 5 | **Generated**: 2025-11-23
## Summary
- ✅ **Recommend APPROVE**: 2
- ❌ **Recommend REJECT**: 1
- ⚠️ **Needs DISCUSSION**: 2
---
## Blocker Analysis
### OCPBUGS-12345: Cluster install fails on AWS ✅ APPROVE
**Recommendation**: APPROVE - This bug meets blocker criteria
**Criteria Matched**:
- ✅ Install/upgrade failure
- ✅ Affects all users
- ✅ No acceptable workaround
**Justification**:
Install failures are strong blockers. This bug prevents cluster installation on AWS, affecting all users attempting AWS deployments. No workaround exists.
**Suggested Action**: Approve as release blocker
---
### OCPBUGS-12346: UI button misaligned ❌ REJECT
**Recommendation**: REJECT - This bug does not meet blocker criteria
**Criteria Matched**:
- ❌ Cosmetic/UI-only issue (not data loss/corruption/unavailability)
- ❌ Severity: Low (must be Important or higher)
**Justification**:
Bugs with severity below Important are never blockers. This is a cosmetic issue with no functional impact.
**Suggested Action**: Reject as release blocker, triage to appropriate sprint
---
## Next Steps
1. Review APPROVE recommendations - add to blocker list
2. Review REJECT recommendations - remove blocker status
3. Discuss unclear cases in triage meeting
IMPORTANT: Either target-version OR --bug must be provided. If neither is provided, the command will error out.
$1 – target-version (required unless --bug is provided)
Target release version to validate blockers for. Format: X.Y (e.g., 4.21, 4.22)
The implementation automatically:
X.Y and X.Y.0 in Target Version, Target Backport Versions, and Affected Version fieldsExamples:
4.21 - Validates active proposed blockers for 4.214.22 - Validates active proposed blockers for 4.22Note: Not required when --bug is provided.
$2 – component-filter (optional) Component name(s) to filter proposed blockers. Supports single or multiple (comma-separated) components.
Examples:
"Hypershift" - Single component"Hypershift,Cluster Version Operator" - Multiple componentsNote: Ignored if --bug is provided. Requires target-version to be specified.
Default: All components for the target version
--bug (optional) Validate a single specific bug by its JIRA issue key.
When provided, analyzes only this bug and ignores both target-version and component-filter.
Examples:
--bug OCPBUGS-36846Note: When --bug is provided, target-version and component-filter are ignored.
Default: Not specified
0 - Success1 - Error querying JIRA or analyzing bugs