GCP HCP team-specific Jira requirements for creating issues in the GCP project (Hypershift on GKE)
Provides GCP HCP team-specific conventions for creating Jira issues in the GCP project.
/plugin marketplace add openshift-eng/ai-helpers/plugin install jira@ai-helpersThis skill inherits all available tools. When active, it can use any tool Claude has access to.
This skill provides GCP HCP (Hypershift on GKE) team-specific conventions for creating Jira issues in the GCP project.
This skill is automatically invoked when:
| Field | Value |
|---|---|
| Project Key | GCP |
| Project Name | GCP Hosted Control Planes (Hypershift on GKE) |
| Issue Types | Story, Epic, Task, Bug, Feature Request |
GCP project uses the same instance-wide custom fields as other Red Hat Jira projects:
| Field | Custom Field ID | Usage | Example |
|---|---|---|---|
| Epic Name | customfield_12311141 | Required when creating Epics | "Multi-cluster metrics aggregation" |
| Epic Link | customfield_12311140 | Link Story/Task → Epic | "GCP-456" |
| Parent Link | customfield_12313140 | Link Epic → Feature | "GCP-100" |
mcp__atlassian__jira_create_issue(
project_key="GCP",
summary="<story summary>",
issue_type="Story",
description="<formatted story description>",
additional_fields={
"customfield_12311140": "GCP-456", # Epic Link - parent epic
"labels": ["ai-generated-jira"],
"security": {"name": "Red Hat Employee"}
}
)
mcp__atlassian__jira_create_issue(
project_key="GCP",
summary="<epic summary>",
issue_type="Epic",
description="<formatted epic description>",
additional_fields={
"customfield_12311141": "Multi-cluster metrics aggregation", # Epic Name (required, same as summary)
"labels": ["ai-generated-jira"],
"security": {"name": "Red Hat Employee"}
}
# NOTE: Do NOT include parent link (customfield_12313140) here.
# Add parent link in a separate update call per "Epic Linking Best Practices" section.
)
When creating an Epic with a parent Feature:
Example:
# Step 1: Create Epic
epic = mcp__atlassian__jira_create_issue(
project_key="GCP",
issue_type="Epic",
summary="Multi-cluster monitoring",
additional_fields={
"customfield_12311141": "Multi-cluster monitoring", # Epic Name
"labels": ["ai-generated-jira"],
"security": {"name": "Red Hat Employee"}
}
)
# Step 2: Link to Feature
mcp__atlassian__jira_update_issue(
issue_key=epic["key"],
fields={},
additional_fields={
"customfield_12313140": "GCP-100" # Parent Link (Feature key)
}
)
The GCP HCP team maintains standardized templates and definitions to ensure consistent, high-quality JIRA tickets. All GCP project issues MUST conform to these standards:
When creating GCP project issues, follow the appropriate template structure:
Story Template - Required structure for all Stories
Epic Template - Required structure for all Epics
Feature Template - Required structure for all Features
When generating issue descriptions for GCP project, incorporate the relevant template structure and ensure acceptance criteria align with the Definition of Done.
Summary: Enable automated backups for GKE hosted control planes
Description:
As a cluster administrator, I want to enable automated backups for my GKE-hosted control planes, so that I can quickly recover from data loss or corruption.
Acceptance Criteria:
- Test that backups can be scheduled daily at a configurable time
- Test that backup retention policy is enforced (30 days default)
- Test that backups can be restored to the same or different GCP project
- Test that backup operations do not interrupt cluster operations
Project: GCP
Issue Type: Story
Component: (optional)
Parent: GCP-456 (Epic)
Labels: ai-generated-jira
Summary: Multi-cluster monitoring and observability
Description:
Implement comprehensive monitoring and observability for GCP-hosted control planes across multiple GKE clusters, enabling operators to detect and respond to issues proactively.
h2. Scope
* Metrics collection from control plane pods
* Central metrics aggregation and storage
* Dashboards for monitoring cluster health
* Alerting framework for critical metrics
* Log aggregation and analysis
h2. Acceptance Criteria
- Test that metrics are collected from all control plane pods
- Test that metrics are available within 30 seconds of generation
- Test that dashboards accurately reflect cluster state
- Test that alerts fire within 2 minutes of anomaly detection
Project: GCP
Issue Type: Epic
Parent: GCP-100 (Feature)
Labels: ai-generated-jira
/jira:create command - Main Jira issue creation commandcntrlplane skill - CNTRLPLANE project conventions (similar structure)hypershift skill - HyperShift team conventions (on AWS/Azure)