skills.rest
openshift-eng
openshift-engOFFICIAL
Explore all skills by this author →
WebsiteGitHub

Fetch Related Triages

Query the Sippy API for related triages and untriaged regressions.

1|Updated Apr 29, 2026
Search Tags:#fetch#openshift#sippy#regressions#component-readiness#triages
One-click install
npx skills add https://github.com/openshift-eng/ga-regression-reports --skill fetch-related-triages
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Fetch Related Triages
Source: https://github.com/openshift-eng/ga-regression-reports/tree/main/.claude/skills/fetch-related-triages
Command: npx skills add https://github.com/openshift-eng/ga-regression-reports --skill fetch-related-triages

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps triage teams quickly locate existing triages and untriaged regressions that are related to a given Component Readiness regression, reducing duplication of effort and speeding resolution.

Core Features & Use Cases

  • Query the Sippy API to surface existing triages that match on test names or shared failing runs for a given regression.
  • Identify open, related regressions that have not yet been triaged to enable coordinated triage work.
  • Provide structured output including triage details (Jira, status) and the regressions linked to each triage.

Quick Start

Run the fetch_related_triages.py script with a regression ID to retrieve related triages and related regressions.

Frequently Asked Questions about Fetch Related Triages

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find existing triages for an OpenShift Component Readiness regression?▼

To find existing triages for an OpenShift Component Readiness regression, query the Sippy API to surface matching triages and open regressions that share tests or failing runs, returning a structured JSON payload with triage IDs and Jira links for deduplication.

What is the best way to prevent duplicate triage effort for OpenShift regressions?▼

The best way to prevent duplicate triage effort for OpenShift regressions is to fetch related triages via the Sippy API, which identifies existing triaged matches and untriaged regressions sharing failing runs to coordinate resolution.

Can I retrieve untriaged regressions related to a specific Component Readiness failure?▼

Yes, you can retrieve untriaged regressions related to a specific Component Readiness failure by querying the Sippy API, which returns open regressions sharing tests or failing runs in a structured JSON payload.

How do I get Jira links and status for triages matching a Sippy regression?▼

You get Jira links and status for matching triages by querying the Sippy API with a regression ID, which returns a structured JSON payload containing triaged_matches with IDs, Jira links, and current status.

What data do I need to run fetch_related_triages.py and retrieve related regressions?▼

To run fetch_related_triages.py and retrieve related regressions, you need a valid Component Readiness regression ID to query the Sippy API for matching triages and untriaged regressions sharing tests or failing runs.

Related Skills

Explore More Software Engineering Skills→
openshift-engopenshift-eng

Fetch Regression Details

Fetch regression details from the Sippy Component Readiness API for a given regression ID.

Official
Intermediate
danievanzyldanievanzyl
1

jira-update

Post concise development updates to Jira tickets via the Jira API.

Community
Intermediate
openshift-engopenshift-eng
112

List Components

Fetch deduplicated, sorted component names from the Sippy API for an OpenShift release.

Community
Basic
openshift-engopenshift-eng

Triage Regression

Creates or updates Component Readiness triage records via the Sippy API to link regressions with a JIRA bug.

Official
Advanced