What is the OCPBUGS skill used for?

It is specifically designed to help developers create standardized, compliant bug reports for the OpenShift project within Jira.

Can I use this skill to create Jira Stories or Tasks?

No, the OCPBUGS project is reserved for bug reports. For Stories or Tasks, users are directed to use the CNTRLPLANE project and associated skills.

How does it handle incorrect versions?

The skill uses MCP tools to fetch available project versions and will suggest the closest valid match if an invalid version is provided.

How does it protect sensitive data?

The skill includes an automated check that stops issue creation if credentials or secrets are detected in the bug description or logs.

Does this skill handle security levels?

Yes, it automatically applies the 'Red Hat Employee' security level to all tickets created in the OCPBUGS project.

OpenShift Jira Bug Management

Name: OpenShift Jira Bug Management
Author: openshift-eng

byopenshift-eng

•

Collaboration Tools

Streamlines the creation of Jira bug reports for the OCPBUGS project with specific OpenShift conventions and field requirements.

About

This skill optimizes the bug reporting workflow for OpenShift product teams by enforcing project-specific Jira conventions within Claude Code. It automates the application of mandatory fields such as 'Affects Version' and 'Target Version' while ensuring security levels are set to 'Red Hat Employee' and labels are correctly applied. By integrating with MCP tools to validate versions and components, the skill reduces manual entry errors and ensures that all tickets meet the standard engineering requirements for the OpenShift ecosystem.

Key Features

Interactive prompts for required 'Affects Version' and 'Target Version' fields
Team-specific component handling and credential sanitization checks
Automatic OCPBUGS project and 'Bug' issue type defaults
Automated security level and 'ai-generated-jira' label application
Version validation and suggestions using jira_get_project_versions
29 GitHub stars

Use Cases

Automating the creation of properly formatted Jira tickets from CLI logs or terminal output
Reporting software defects encountered in specific OpenShift releases
Standardizing bug descriptions across different OpenShift engineering teams

About

Key Features

Interactive prompts for required 'Affects Version' and 'Target Version' fields
Team-specific component handling and credential sanitization checks
Automatic OCPBUGS project and 'Bug' issue type defaults
Automated security level and 'ai-generated-jira' label application
Version validation and suggestions using jira_get_project_versions
29 GitHub stars

Use Cases

Automating the creation of properly formatted Jira tickets from CLI logs or terminal output
Reporting software defects encountered in specific OpenShift releases
Standardizing bug descriptions across different OpenShift engineering teams