jira

Fetches Jira ticket details via CLI and returns a flat JSON object.

Updated Jun 4, 2022
One-click install
npx skills add https://github.com/toh995/dotfiles --skill jira-toh995
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira
Source: https://github.com/toh995/dotfiles/tree/main/.claude/skills/jira
Command: npx skills add https://github.com/toh995/dotfiles --skill jira-toh995

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, curl, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill enables you to fetch live Jira ticket data from Jira Cloud via a CLI, returning a clean, flat JSON payload for easy automation and integration.

Core Features & Use Cases

  • Retrieve key, summary, type, status, priority, assignee, labels, description, and links for Jira issues, including related links and child issues.
  • Produce a compact, machine-readable JSON structure suitable for dashboards, automation, and reporting across Jira tickets, epics, and linked items.
  • Use Case: Quickly populate a status dashboard with up-to-date ticket details or feed incident pipelines with accurate issue metadata.

Quick Start

Run the Jira tool to fetch a ticket with its key, for example: ~/.claude/skills/jira/scripts/jira-tool get SOX-1234

Frequently Asked Questions about jira

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

FAQPage Schema
How do I fetch Jira ticket details as JSON from the command line?

You can fetch Jira ticket details as JSON via CLI by running the jira-tool get command with a ticket key. It queries the Jira Cloud REST v2 search endpoint and returns a flat JSON object containing summary, status, assignee, priority, labels, and issuelinks.

What do I need to configure to query Jira Cloud via CLI?

Querying Jira Cloud via CLI requires configuring your base_url and a Jira API token in assets/config and assets/.token. You also need curl and jq installed as dependencies to execute the requests and parse the returned JSON payloads.

Can I retrieve linked issues and child tickets for Jira epics?

Yes, you can retrieve linked issues and child tickets for Jira epics. The tool queries the Jira REST v2 endpoint and extracts fields including issuelinks and related child issues, returning them within a clean, flat JSON structure for automation and dashboards.

What is the best way to get Jira issue metadata for a status dashboard?

The best way to get Jira issue metadata for a status dashboard is using a CLI tool that returns a compact, machine-readable JSON structure. This approach fetches live ticket data including status, priority, and assignee directly from Jira Cloud for easy integration.

Does this Jira CLI tool support JQL search for automation pipelines?

The Jira CLI tool uses the Jira REST v2 search/jql endpoint to fetch issue data, returning a clean JSON payload. This makes it suitable for feeding incident pipelines and automation workflows with accurate issue metadata based on JQL queries.

What are the limitations of using CLI to fetch Jira issue data as JSON?

Limitations include requiring pre-configured base_url and API token files, and dependencies on curl and jq. The tool focuses on retrieving specific fields like summary, status, and issuelinks rather than supporting complex interactive Jira session management.