jira-fetch

Name: jira-fetch
Availability: InStock
Author: mczkzk

Fetch JIRA ticket details and save them as Markdown files.

Updated Jul 8, 2017

Search Tags:#automation #markdown #api #fetch #jira #ticket

Ready to run

npx skills add https://github.com/mczkzk/dotfiles --skill jira-fetch-mczkzk

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jira-fetch
Source: https://github.com/mczkzk/dotfiles/tree/main/dot_claude/skills/jira-fetch
Command: npx skills add https://github.com/mczkzk/dotfiles --skill jira-fetch-mczkzk

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the retrieval of JIRA ticket information, saving you from manually looking up details across different interfaces.

Core Features & Use Cases

Fetch Ticket Data: Retrieves summary, status, assignee, description, comments, attachments, and related issues for specified JIRA tickets.
Organized Storage: Saves fetched JIRA ticket data into structured Markdown files within your project's .claude/plans/ directory.
Attachment Handling: Downloads image attachments and links them within the generated Markdown.
Use Case: When starting a new development task, use this Skill to quickly pull all relevant information about the JIRA ticket, including its description, comments, and any linked subtasks, directly into your project's context.

Quick Start

Use the jira-fetch skill to get details for JIRA ticket PROJ-123.

Frequently Asked Questions about jira-fetch

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

FAQPage Schema

How do I fetch JIRA ticket details and save them as Markdown?▼

To fetch JIRA ticket details as Markdown, use a skill that retrieves summary, status, assignee, description, comments, and attachments, then stores the data in `.claude/plans/{ISSUE_KEY}/jira.md` within your project directory. It automatically downloads linked image attachments alongside the file.

What do I need to configure before retrieving JIRA ticket information via API?▼

Before retrieving JIRA ticket information via API, you need to configure your JIRA API credentials in the `~/.claude/.jira.env` file. You also need a project-specific prefix file to handle ticket key normalization during the fetch process.

Does this JIRA ticket fetcher work with command line tools like curl and jq?▼

Yes, this JIRA ticket fetcher works with command line tools and requires curl, jq, git, and base64 installed as dependencies. It leverages these scripts to interact with the JIRA API and process the returned ticket data.

Can I download JIRA ticket attachments and images locally for offline context?▼

Yes, you can download JIRA ticket attachments and images locally. The skill retrieves image attachments from the specified tickets and saves them directly within your local project directory structure, linking them inside the generated Markdown file.

What is the best way to pull JIRA subtasks and issue links into my project context?▼

The best way to pull JIRA subtasks and issue links into your project context is using an automated fetch skill that retrieves related issues and stores them in structured Markdown files. This organizes all relevant ticket data locally for immediate development reference.

Why are my JIRA ticket keys not normalizing correctly when fetching data?▼

JIRA ticket keys may not normalize correctly if the project-specific prefix file is missing or improperly configured. The fetch process relies on this file to standardize ticket keys before querying the API and saving the Markdown output.