HyperShift Jira Conventions

Automate Jira issue creation for HyperShift by using smart component detection that identifies ARO, ROSA, or platform-agnostic requirements from your issue summary or description. The Skill automatically applies team-specific conventions, default versions, labels, and security settings when HyperShift-related keywords or components are detected, eliminating manual configuration.

Component detection examines your issue summary and description for HyperShift keywords—HyperShift, ARO HCP, ROSA HCP, or hosted control plane—and automatically assigns the correct platform-specific component: HyperShift/ARO, HyperShift/ROSA, or platform-agnostic. Interactive prompts help resolve ambiguous cases.

This Skill enforces HyperShift conventions for CNTRLPLANE and OCPBUGS issue types by automatically setting target versions, affects versions, labels, and security fields based on detected platform requirements. It applies consistent defaults across all HyperShift-related tickets.

Yes. This Skill detects whether your issue targets ARO HCP, ROSA HCP, or platform-agnostic HyperShift and assigns the appropriate component and field defaults for each. A single workflow handles both platforms with automatic differentiation.

Yes. This Skill integrates with standard Jira issue creation workflows and applies HyperShift conventions automatically when triggered by relevant keywords or component selection. It works within your existing issue-tracking process without replacing core Jira functionality.

When the platform cannot be auto-detected, this Skill presents interactive prompts to gather missing details, allowing you to clarify whether the issue targets ARO, ROSA, or a platform-agnostic component before finalizing the ticket.