Summarize JIRAs

Query and summarize JIRA bugs by status, priority, and component.

112|305|Updated Oct 10, 2025

Search Tags:#jira #summary-statistics #bug-tracking #bug-analysis #component-health

Ready to run

npx skills add https://github.com/openshift-eng/ai-helpers --skill summarize-jiras

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Summarize JIRAs
Source: https://github.com/openshift-eng/ai-helpers/tree/main/plugins/component-health/skills/summarize-jiras
Command: npx skills add https://github.com/openshift-eng/ai-helpers --skill summarize-jiras

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill eliminates the manual effort of analyzing JIRA bug backlogs by automatically generating comprehensive summary statistics and component health reports.

Core Features & Use Cases

Bug Analysis: Automatically count and categorize bugs by status, priority, and component.
Trend Tracking: Monitor bug velocity with opened/closed metrics over the last 30 days.
Use Case: Imagine you need to assess the health of the kube-apiserver component. Use this Skill to get immediate counts of open bugs, their priority distribution, and recent activity trends.

Quick Start

Use the Summarize JIRAs skill to analyze all open bugs in the OCPBUGS project and provide a summary breakdown by component and status.

Frequently Asked Questions about Summarize JIRAs

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

FAQPage Schema

How do I summarize JIRA bugs by component and priority?▼

Summarize JIRA bugs by querying your project with filters for component, status, and priority to generate structured counts and health reports. The Skill automatically categorizes open versus closed bugs and breaks down distribution across components, giving you immediate visibility into backlog composition.

Can I track bug velocity and recent JIRA activity trends?▼

Yes. The Skill monitors bug velocity by analyzing opened and closed bug counts over the last 30 days, letting you spot trends in how fast bugs are being resolved or accumulating within specific components.

What JIRA credentials and setup do I need to analyze bugs?▼

You need Python 3, a JIRA URL, and a personal access token. Provide credentials via JIRA_URL and JIRA_PERSONAL_TOKEN environment variables so the Skill can authenticate and query your JIRA project without manual data export.

How do I assess component health across my bug backlog?▼

Use the Skill to filter bugs by component and analyze status and priority breakdowns for each. This produces a component health snapshot showing which areas have the most open bugs and where priority work is concentrated.

Does this work for analyzing large JIRA projects?▼

Yes. The Skill uses JIRA's query and filtering API to handle projects of any size, returning structured summary statistics without requiring manual spreadsheet export or scripting.

What if I need to filter bugs opened or closed in a specific time window?▼

The Skill supports time-window filtering for bugs opened or closed in the last 30 days as a built-in filter option, letting you isolate recent activity and trend velocity within that period.