List JIRAs

Query raw JIRA bug data via the JIRA REST API with optional filters.

112|305|Updated Oct 10, 2025
One-click install
npx skills add https://github.com/openshift-eng/ai-helpers --skill list-jiras
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: List JIRAs
Source: https://github.com/openshift-eng/ai-helpers/tree/main/plugins/component-health/skills/list-jiras
Command: npx skills add https://github.com/openshift-eng/ai-helpers --skill list-jiras

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill eliminates the manual effort of querying JIRA and provides complete raw issue data for custom processing and analysis.

Core Features & Use Cases

  • Raw Data Access: Retrieve complete JIRA issue information with all fields and metadata.
  • Flexible Filtering: Query by project, component, status, and include closed bugs.
  • Use Case: Imagine you need to analyze bug trends across multiple components. Use this Skill to fetch all open and recently closed bugs for the kube-apiserver and etcd components, then pass the data to summary tools for insights.

Quick Start

Use the List JIRAs skill to fetch all open bugs from the OCPBUGS project.

Frequently Asked Questions about List JIRAs

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

FAQPage Schema
How do I fetch raw JIRA bug data for custom analysis?

Fetch raw JIRA bug data using the List JIRAs Skill to query complete issue details from the JIRA REST API. It retrieves all fields and metadata for a specified project with optional filters by component, status, and closed-bug inclusion, enabling downstream processing and analysis without manual export.

Can I query JIRA data by component and status?

Yes. The List JIRAs Skill supports flexible filtering by project, component, status, and include-closed flag. This lets you isolate bugs from specific components or workflow stages, then pass filtered results to analysis tools for trend tracking or custom reporting.

What authentication does the JIRA API integration require?

List JIRAs requires Python 3.6+, network access to your JIRA instance, and two environment variables: JIRA_URL and JIRA_PERSONAL_TOKEN. Set these credentials before querying to authenticate API calls and retrieve project data.

How do I automate bug trend analysis across multiple JIRA components?

Use List JIRAs to fetch all open and recently closed bugs for target components, then pass the raw issue data to downstream analysis or summary tools. This workflow automates data gathering and enables custom processing without manual JIRA exports.

Does this Skill work with OpenShift or Red Hat JIRA instances?

List JIRAs works with any JIRA instance accessible via REST API and properly configured with JIRA_URL and JIRA_PERSONAL_TOKEN environment variables. It's commonly used for OpenShift projects like OCPBUGS but adapts to any JIRA deployment.

What happens when I set the limit parameter on JIRA queries?

The limit parameter controls how many issues the Skill returns from your JIRA query. This lets you cap result size for large projects, manage data volume, or test queries before retrieving complete datasets for analysis.