JIRA Integration

Convert JIRA tickets into local story files via API or web scraping.

1|Updated Oct 20, 2025
One-click install
npx skills add https://github.com/normcrandall/claudeskills --skill jira-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: JIRA Integration
Source: https://github.com/normcrandall/claudeskills/tree/main/jira
Command: npx skills add https://github.com/normcrandall/claudeskills --skill jira-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill seamlessly imports JIRA tickets (stories, tasks, bugs) into local, actionable story files, supporting both API and web scraping for maximum flexibility. It eliminates manual data entry and ensures traceability between your JIRA backlog and local development workflow.

Core Features & Use Cases

  • Flexible Import: Fetches tickets via JIRA API (requiring credentials) or through web scraping (from a JIRA URL or pasted HTML), adapting to your access level.
  • Local Story Conversion: Transforms JIRA tickets into a standardized local story format, complete with descriptions, acceptance criteria, tasks, and JIRA context.
  • Bulk Import: Supports importing multiple tickets via JQL queries or a list of IDs when using the API.
  • Optional Dev Kickoff: Can automatically invoke the dev skill to start implementation immediately after a ticket is imported.
  • Use Case: Import an entire sprint's backlog from JIRA with a single command, converting all tickets into local stories ready for development, saving hours of manual setup.

Quick Start

Import a single JIRA ticket via URL (web scraping)

Skill(command: "jira")

Provide JIRA URL, e.g., "https://your-company.atlassian.net/browse/SMOKE-123"

Frequently Asked Questions about JIRA Integration

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

FAQPage Schema
How do I import JIRA tickets into local story files?

Import JIRA tickets by providing a ticket URL or JIRA credentials. The Skill converts tickets (stories, tasks, bugs, epics) into local story files with descriptions, acceptance criteria, and traceability to JIRA IDs, supporting both API and web scraping methods.

Can I import multiple JIRA tickets at once?

Yes, bulk import is supported via JQL queries or ticket ID lists when using the JIRA API. This lets you import an entire sprint's backlog in a single operation, converting all tickets to local stories ready for development.

Do I need JIRA API credentials to import tickets?

No, the Skill offers two access methods: API import (requires credentials) and web scraping (needs only a JIRA URL or pasted HTML). Choose based on your access level and environment constraints.

What happens to ticket data when converted to local stories?

Ticket data is transformed into standardized local story format, preserving descriptions, acceptance criteria, tasks, and maintaining a link back to the original JIRA ID for full traceability between your backlog and development workflow.

Can the import process automatically start development?

Yes, the Skill includes optional dev kickoff automation that invokes the `dev` skill immediately after importing a ticket, letting you move directly from ticket import to implementation without manual workflow steps.

What JIRA issue types does this support?

The Skill handles stories, tasks, bugs, and epics, adapting the conversion process to each issue type's structure and ensuring all ticket varieties integrate smoothly into your local development workflow.