JIRA Release Blocker Validator

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.

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.

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.

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.

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.

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.