jira-integration

Retrieve and update Jira tickets via REST API v3 or MCP.

Updated Sep 13, 2025
One-click install
npx skills add https://github.com/llmh333/employee_management_spring --skill jira-integration-llmh333
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-integration
Source: https://github.com/llmh333/employee_management_spring/tree/main/.gemini/skills/jira-integration
Command: npx skills add https://github.com/llmh333/employee_management_spring --skill jira-integration-llmh333

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams retrieve and operationally manage Jira tickets without switching tools, reducing the time spent gathering requirements and keeping issue status and communication up to date.

Core Features & Use Cases

  • Issue retrieval and analysis: Fetch Jira issues and extract requirements, acceptance criteria, test types, edge cases, and structured outputs for engineering execution planning.
  • Status transitions and commenting: Transition issues across workflow states and add progress comments that document implementation steps and test results.
  • Search and traceability: Run JQL searches and link related development artifacts like pull requests/branches to maintain end-to-end context.

Quick Start

Use the jira-integration skill to fetch and summarize the ticket PROJ-1234, including testable requirements, acceptance criteria, and recommended next update steps.

Frequently Asked Questions about jira-integration

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

FAQPage Schema
How do I fetch Jira tickets and extract acceptance criteria using JQL search?

JQL search retrieves Jira tickets to extract requirements, acceptance criteria, and test types. It fetches issues based on custom queries, providing structured outputs for engineering execution planning and requirement understanding.

What environment variables do I need to access the Jira API v3?

Accessing the Jira API v3 requires three environment variables: JIRA_URL, JIRA_EMAIL, and JIRA_API_TOKEN. These credentials authenticate requests for retrieving and updating issues directly through the REST API v3 endpoint.

Can I transition Jira issues and add progress comments from my workflow automation?

You can transition Jira issues across workflow states and add progress comments from workflow automation. This functionality documents implementation steps and test results, updating issue status as work progresses from start through completion.

Does this approach work with mcp-atlassian or do I need direct API integration?

This approach works with both mcp-atlassian and direct API integration. You can choose MCP for Atlassian integration or use the direct REST API v3 with the required JIRA_URL, JIRA_EMAIL, and JIRA_API_TOKEN environment variables for access.

How do I link pull requests and branches to Jira issues for end-to-end traceability?

Linking pull requests and branches to Jira issues for end-to-end traceability is achieved by running JQL searches and updating tickets. This maintains development artifact context alongside issue status and communication updates.