jira-fetch

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.

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.

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.

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.

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.

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.