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

Fetch JIRA Issue

Fetch JIRA issue details and classify progress for regression triage.

1|Updated Apr 29, 2026
Search Tags:#automation#api#regression#jira#issue#progress
One-click install
npx skills add https://github.com/openshift-eng/ga-regression-reports --skill fetch-jira-issue
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Fetch JIRA Issue
Source: https://github.com/openshift-eng/ga-regression-reports/tree/main/.claude/skills/fetch-jira-issue
Command: npx skills add https://github.com/openshift-eng/ga-regression-reports --skill fetch-jira-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fetches comprehensive JIRA issue data to support regression analysis and progress tracking.

Core Features & Use Cases

  • Retrieve key fields such as status, priority, resolution, assignee, reporter, components, fix versions, created and updated timestamps.
  • Extract comments and derive linked PRs from comment bodies for traceability.
  • Classify progress into ACTIVE, STALLED, NEEDS_ATTENTION, or RESOLVED to aid triage and status reporting.
  • Use Case: When assessing a regression, pull the issue details and a concise progress assessment to inform remediation priorities.

Quick Start

Run the script with a Jira key to fetch the issue data and display it in JSON or a readable summary.

Frequently Asked Questions about Fetch JIRA Issue

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

FAQPage Schema
How do I fetch JIRA issue details and comments for regression analysis?▼

You can fetch JIRA issue details by authenticating against the JIRA REST API with a username and API token. The Skill retrieves status, assignee, comments, and linked PRs to support regression analysis.

What is the best way to track JIRA bug progress and linked PRs during triage?▼

Tracking JIRA bug progress involves classifying issue status into ACTIVE, STALLED, NEEDS_ATTENTION, or RESOLVED. This Skill extracts linked PRs from comment bodies to provide a concise progress assessment for triage.

Do I need a JIRA API token to retrieve issue status and fix versions?▼

Yes, you need a JIRA API token and username to authenticate against the JIRA REST API. This authentication is required to retrieve key fields including status, priority, resolution, components, and fix versions.

How does JIRA issue progress classification work for stalled or active bugs?▼

JIRA issue progress classification evaluates status, assignee, comments, and linked PRs to categorize issues as ACTIVE, STALLED, NEEDS_ATTENTION, or RESOLVED. This classification aids triage and status reporting for regression bugs.

Can I extract linked pull requests from JIRA comments via the REST API?▼

Yes, you can extract linked PRs from JIRA comment bodies by fetching issue data through the REST API. The Skill parses comment text to derive linked PRs for traceability during regression analysis.

Related Skills

Explore More Software Engineering Skills→
JuanMS20JuanMS20

github-auth

Configure GitHub authentication for Hermes Agent using git, gh CLI, or SSH credentials.

Community
Intermediate
EmergenceAIEmergenceAI
2

jira-update

Automate Jira issue updates with pull request links and test results.

Official
Advanced
joe-watkinsjoe-watkins
1

a11y-issue-writer

Convert axe-core violations into standardized Jira-ready issue reports.

Community
Intermediate
sethdfordsethdford
2

JQL Query Builder

Construct and validate JQL queries for Jira issue searches.

Community
Intermediate