jira-integration

Retrieve, analyze, and update Jira tickets via MCP tools or REST API calls.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/freedom909/real-estate-saas --skill jira-integration-freedom909
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jira-integration
Source: https://github.com/freedom909/real-estate-saas/tree/main/.trae/skills/jira-integration
Command: npx skills add https://github.com/freedom909/real-estate-saas --skill jira-integration-freedom909

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mcp-atlassian.

What problem does it solve? Manually switching between your coding environment and Jira to read requirements, post updates, and change ticket statuses breaks developer flow and leads to stale tickets. This Skill lets you fetch, analyze, comment on, and transition Jira issues directly from your AI coding workflow. ## Core Features & Use Cases - Ticket Retrieval & Analysis: Fetch full issue details and extract testable requirements, acceptance criteria, edge cases, and test scenarios in a structured format. - Ticket Updates: Add progress comments using ready-made templates, transition statuses (To Do → In Progress → Done), and link branches or pull requests to issues. - JQL Search: Query issues by project, status, or sprint using JQL through MCP tools or direct REST API calls. - Use Case: You are assigned ticket PROJ-1234. Ask your AI agent to fetch the ticket, extract acceptance criteria into a test plan, transition it to "In Progress", and post a comment with your branch name — all without leaving your editor. ## Quick Start Ask the AI to fetch Jira ticket PROJ-1234, summarize its requirements and acceptance criteria, and transition it to In Progress.

Frequently Asked Questions about jira-integration

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

FAQPage Schema
How do I fetch a Jira ticket from the command line?▼

Use curl with basic auth against the Jira REST API v3: curl -u "$JIRA_EMAIL:$JIRA_API_TOKEN" "$JIRA_URL/rest/api/3/issue/PROJ-1234". Pipe the response through jq to extract fields like summary, status, priority, and assignee.

How do I transition a Jira issue status via API?▼

First call GET /rest/api/3/issue/{key}/transitions to list available transition IDs, since they vary per project workflow. Then POST to the same endpoint with {"transition": {"id": "TRANSITION_ID"}} in the request body.

MCP server vs direct REST API for Jira integration?▼

The mcp-atlassian MCP server exposes ready-made tools like jira_get_issue and jira_transition_issue directly to your AI agent, which is the recommended approach. Direct REST API calls via curl work as a fallback when MCP is unavailable.

Why does my Jira API call return 401 Unauthorized?▼

A 401 error means your API token is invalid or expired. Regenerate a token at id.atlassian.com/manage-profile/security/api-tokens and update the JIRA_API_TOKEN environment variable, ensuring it is never committed to source code.

How do I fix spawn uvx ENOENT when configuring the Jira MCP server?▼

This error means your IDE cannot find uvx on PATH. Use the full path to the binary (for example ~/.local/bin/uvx) in your MCP config, or set PATH in your shell profile such as ~/.zprofile.