CNTRLPLANE Jira Conventions

CNTRLPLANE Jira conventions enforce consistent issue creation by normalizing version formats, linking parent epics, handling components, and populating mandatory fields. This Skill applies these rules automatically when you create Stories, Epics, Features, and Tasks for OpenShift teams, eliminating manual formatting errors.

Version normalization converts user inputs like "4.22" or "OCP 4.22" into the standard Jira format "openshift-4.22". This ensures consistent version tracking across HyperShift, Cluster Infrastructure, Networking, Storage, and other CNTRLPLANE teams.

Parent linking handles complex relationships between features, epics, stories, and tasks using CNTRLPLANE-specific custom fields. The Skill maps these relationships automatically, ensuring stories connect to the correct epic without manual field lookups.

Yes. This Skill applies to Stories, Epics, Features, and Tasks across OpenShift control plane teams. It covers target version normalization, Epic/Parent linking, component handling, and mandatory field validation for HyperShift, Cluster Infrastructure, Networking, Storage, and related CNTRLPLANE teams.

The Skill includes pre-validation and fallback creation strategies to ensure compliant ticket generation even when optional inputs are incomplete. It enforces mandatory fields while handling edge cases across custom field mappings.

Yes. The Skill manages CNTRLPLANE-specific custom field mappings including customfield_12319940, customfield_12311140, customfield_12313140, and customfield_epicname, ensuring fields populate correctly without manual configuration.