JIRA Release Blocker Validator

Validates proposed OCPBUGS Jira release blockers and outputs APPROVE, REJECT or DISCUSS recommendations.

112|305|Updated Oct 10, 2025

Search Tags:#automation #jira #release-management #quality-assurance #openshift #blocker-validation

Ready to run

npx skills add https://github.com/openshift-eng/ai-helpers --skill jira-release-blocker-validator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: JIRA Release Blocker Validator
Source: https://github.com/openshift-eng/ai-helpers/tree/main/plugins/jira/skills/jira-validate-blockers
Command: npx skills add https://github.com/openshift-eng/ai-helpers --skill jira-release-blocker-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates guesswork in release management by automatically validating proposed JIRA blockers against Red Hat OpenShift criteria, ensuring only legitimate issues block releases.

Core Features & Use Cases

Automated Blocker Analysis: Scores proposed blockers against official OpenShift release criteria to generate APPROVE/REJECT/DISCUSS recommendations.
CI-Only Detection: Identifies infrastructure-only issues that shouldn't block product releases.
Workaround Assessment: Evaluates whether proposed workarounds meet idempotent, scalable, and timely requirements.
Use Case: When preparing for an OpenShift 4.21 release, use this Skill to validate all proposed blockers and get instant recommendations with detailed justifications.

Quick Start

Use the JIRA Release Blocker Validator to analyze proposed blockers for OpenShift version 4.21.

Frequently Asked Questions about JIRA Release Blocker Validator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I validate proposed release blockers in JIRA before approving them?▼

Release blocker validation scores proposed blockers against OpenShift criteria to generate APPROVE, REJECT, or DISCUSS recommendations. Query the OCPBUGS project by target version and component, retrieve blocker fields and status, then apply validation logic to determine legitimacy and impact on release readiness.

Can I identify infrastructure-only issues that shouldn't block product releases?▼

CI-only detection filters issues affecting only build infrastructure from product blockers. The validation analyzes issue scope and components to distinguish CI-specific problems, preventing unnecessary release holds on infrastructure-only failures.

What's the best way to assess whether a workaround meets release blocker requirements?▼

Workaround assessment evaluates proposed solutions against idempotent, scalable, and timely criteria. The validation scores each workaround's operational viability to determine if it sufficiently mitigates the blocker or if the issue requires upstream resolution.

How do I get automated recommendations for OpenShift release blockers at scale?▼

Automated blocker analysis scores multiple proposed blockers against OpenShift release criteria simultaneously, filtering by target version and components. The Skill queries JIRA via JQL, retrieves priority and severity fields, and produces batch recommendations with justifications.

Does release blocker validation work with custom JIRA fields and labels?▼

Yes, the validator retrieves custom release blocker fields, target version fields, labels, and component data from OCPBUGS. It constructs JQL queries that reference these fields to filter and analyze blocker eligibility for specific OpenShift versions.

When should I not rely on automated blocker validation?▼

Automated validation applies to OCPBUGS project blockers with clear criteria. Complex business decisions, cross-project dependencies, or issues outside OpenShift scope may require manual review. Use DISCUSS recommendations as escalation points for edge cases.