Can I see linked issues or blockers?

Yes, the skill extracts relationship data, showing you which issues block the current ticket, which are blocked by it, and its parent Epic context.

Is this Jira integration read-only?

Yes, the Jira skill is strictly read-only, allowing Claude to fetch context and details without the risk of accidentally modifying or deleting your Jira tickets.

How does Claude recognize which Jira ticket to fetch?

The skill uses regex patterns to automatically identify issue keys (e.g., 'PLAT-123') within your conversation and proactively offers to retrieve the data.

What credentials do I need to set up?

You need to set two environment variables: JIRA_EMAIL (your Atlassian email) and JIRA_TOKEN (your API token generated from Atlassian security settings).

Jira Integration for Claude Code

Name: Jira Integration for Claude Code
Author: resolve-io

byresolve-io

•

Herramientas de Colaboración

Fetches Jira issue context and acceptance criteria directly into the development workflow using automatic issue key detection.

Acerca de

The Jira skill provides a seamless, read-only integration that allows Claude to automatically recognize issue keys and retrieve comprehensive ticket data via the Jira REST API. By pulling in details from Epics, Stories, and Bugs—including acceptance criteria, comment history, and dependency links—it ensures Claude has full project context for implementing features or fixing bugs without manual copy-pasting. It operates securely through environment variables and leverages curl for reliable API communication.

Características Principales

Automatic detection of Jira issue keys like PROJ-123 in conversation
Retrieves full ticket details including summary, status, and acceptance criteria
1 GitHub stars
Maps issue hierarchies from Epics to subtasks and identifies blockers
Fetches recent comment history to provide technical and customer context
Secure authentication using system environment variables and curl

Casos de Uso

Implementing features by pulling precise acceptance criteria from a Jira story
Debugging issues by retrieving reproduction steps and comments from a Jira bug report
Decomposing complex Epics into actionable developer tasks by analyzing story links

Acerca de

Características Principales

Automatic detection of Jira issue keys like PROJ-123 in conversation
Retrieves full ticket details including summary, status, and acceptance criteria
1 GitHub stars
Maps issue hierarchies from Epics to subtasks and identifies blockers
Fetches recent comment history to provide technical and customer context
Secure authentication using system environment variables and curl

Casos de Uso

Implementing features by pulling precise acceptance criteria from a Jira story
Debugging issues by retrieving reproduction steps and comments from a Jira bug report
Decomposing complex Epics into actionable developer tasks by analyzing story links