Skip to main content
jira-integration Jira API patterns via MCP or direct REST calls for retrieving tickets, extracting acceptance criteria, adding comments, transitioning status, and JQL search. USE WHEN reading Jira tickets, updating ticket status, or linking branches and MRs to issues from a coding workflow.
Aller à l'installation Skills Marketplace Découvrez et explorez les compétences IA créées par la communauté.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Afficher les détails du prompt Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
npx skills add https://github.com/Sheshiyer/skill-clusters --skill jira-integrationLa commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.
Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.
Télécharger Zip Téléchargement... Métiers associés SOC
Basé sur la classification professionnelle SOC
name jira-integration description Jira API patterns via MCP or direct REST calls for retrieving tickets, extracting acceptance criteria, adding comments, transitioning status, and JQL search. USE WHEN reading Jira tickets, updating ticket status, or linking branches and MRs to issues from a coding workflow. origin ECC cluster agentic-ops version 1.0.0
Jira Integration Skill
Retrieve, analyze, and update Jira tickets directly from your AI coding workflow. Supports both MCP-based (recommended) and direct REST API approaches.
When to Activate
Fetching a Jira ticket to understand requirements
Extracting testable acceptance criteria from a ticket
Adding progress comments to a Jira issue
Transitioning a ticket status (To Do → In Progress → Done)
Linking merge requests or branches to a Jira issue
Searching for issues by JQL query
Prerequisites
Option A: MCP Server (Recommended)
Install the mcp-atlassian MCP server. This exposes Jira tools directly to your AI agent.
Requirements:
uvx (from uv), installed via your package manager or the official uv installation documentationAdd to your MCP config (e.g., ~/.claude.json → mcpServers):
{
"jira" : {
"command" : "uvx" ,
"args" : [ "mcp-atlassian==0.21.0" ] ,
"env" : {
"JIRA_URL" : "https://YOUR_ORG.atlassian.net" ,
"JIRA_EMAIL" : "your.email@example.com" ,
"JIRA_API_TOKEN" : "your-api-token"
} ,
"description" : "Jira issue tracking — search, create, update, comment, transition"
}
}
Security: Never hardcode secrets. Prefer setting JIRA_URL, JIRA_EMAIL, and JIRA_API_TOKEN in your system environment (or a secrets manager). Only use the MCP env block for local, uncommitted config files.
Option B: Direct REST API If MCP is not available, use the Jira REST API v3 directly via curl or a helper script.
Required environment variables:
Variable Description JIRA_URLYour Jira instance URL (e.g., https://yourorg.atlassian.net) JIRA_EMAILYour Atlassian account email JIRA_API_TOKENAPI token from id.atlassian.com
Store these in your shell environment, secrets manager, or an untracked local env file. Do not commit them to the repo.
MCP Tools Reference When the mcp-atlassian MCP server is configured, these tools are available:
Tool Purpose Example jira_searchJQL queries project = PROJ AND status = "In Progress"jira_get_issueFetch full issue details by key PROJ-1234jira_create_issueCreate issues (Task, Bug, Story, Epic) New bug report jira_update_issueUpdate fields (summary, description, assignee) Change assignee jira_transition_issueChange status Move to "In Review" jira_add_commentAdd comments Progress update jira_get_sprint_issuesList issues in a sprint Active sprint review jira_create_issue_linkLink issues (Blocks, Relates to) Dependency tracking jira_get_issue_development_infoSee linked PRs, branches, commits Dev context
Tip: Always call jira_get_transitions before transitioning — transition IDs vary per project workflow.
Direct REST API Reference
Fetch a Ticket curl -s -u "$JIRA_EMAIL :$JIRA_API_TOKEN " \
-H "Content-Type: application/json" \
"$JIRA_URL /rest/api/3/issue/PROJ-1234" | jq '{
key: .key,
summary: .fields.summary,
status: .fields.status.name,
priority: .fields.priority.name,
type: .fields.issuetype.name,
assignee: .fields.assignee.displayName,
labels: .fields.labels,
description: .fields.description
}'
Fetch Comments curl -s -u "$JIRA_EMAIL :$JIRA_API_TOKEN " \
-H "Content-Type: application/json" \
"$JIRA_URL /rest/api/3/issue/PROJ-1234?fields=comment" | jq '.fields.comment.comments[] | {
author: .author.displayName,
created: .created[:10],
body: .body
}'
Add a Comment curl -s -X POST -u "$JIRA_EMAIL :$JIRA_API_TOKEN " \
-H "Content-Type: application/json" \
-d '{
"body": {
"version": 1,
"type": "doc",
"content": [{
"type": "paragraph",
"content": [{"type": "text", "text": "Your comment here"}]
}]
}
}' \
"$JIRA_URL /rest/api/3/issue/PROJ-1234/comment"
Transition a Ticket
curl -s -u "$JIRA_EMAIL :$JIRA_API_TOKEN " \
"$JIRA_URL /rest/api/3/issue/PROJ-1234/transitions" | jq '.transitions[] | {id, name: .name}'
curl -s -X POST -u "$JIRA_EMAIL :$JIRA_API_TOKEN " \
-H "Content-Type: application/json" \
-d '{"transition": {"id": "TRANSITION_ID"}}' \
"$JIRA_URL /rest/api/3/issue/PROJ-1234/transitions"
Search with JQL curl -s -G -u "$JIRA_EMAIL :$JIRA_API_TOKEN " \
--data-urlencode "jql=project = PROJ AND status = 'In Progress'" \
"$JIRA_URL /rest/api/3/search"
Analyzing a Ticket When retrieving a ticket for development or test automation, extract:
1. Testable Requirements
Functional requirements — What the feature doesAcceptance criteria — Conditions that must be metTestable behaviors — Specific actions and expected outcomesUser roles — Who uses this feature and their permissionsData requirements — What data is neededIntegration points — APIs, services, or systems involved
2. Test Types Needed
Unit tests — Individual functions and utilitiesIntegration tests — API endpoints and service interactionsE2E tests — User-facing UI flowsAPI tests — Endpoint contracts and error handling
3. Edge Cases & Error Scenarios
Invalid inputs (empty, too long, special characters)
Unauthorized access
Network failures or timeouts
Concurrent users or race conditions
Boundary conditions
Missing or null data
State transitions (back navigation, refresh, etc.)
4. Structured Analysis Output Ticket: PROJ-1234
Summary: [ticket title]
Status: [current status]
Priority: [High/Medium/Low]
Test Types: Unit, Integration, E2E
Requirements:
1. [requirement 1]
2. [requirement 2]
Acceptance Criteria:
- [ ] [criterion 1]
- [ ] [criterion 2]
Test Scenarios:
- Happy Path: [description]
- Error Case: [description]
- Edge Case: [description]
Test Data Needed:
- [data item 1]
- [data item 2]
Dependencies:
- [dependency 1]
- [dependency 2]
Updating Tickets
When to Update Workflow Step Jira Update Start work Transition to "In Progress" Tests written Comment with test coverage summary Branch created Comment with branch name PR/MR created Comment with link, link issue Tests passing Comment with results summary PR/MR merged Transition to "Done" or "In Review"
Comment Templates Starting implementation for this ticket.
Branch: feat/PROJ-1234-feature-name
Automated tests implemented:
Unit Tests:
- [test file 1] — [what it covers]
- [test file 2] — [what it covers]
Integration Tests:
- [test file] — [endpoints/flows covered]
All tests passing locally. Coverage: XX%
Pull request created:
[PR Title](https://github.com/org/repo/pull/XXX)
Ready for review.
Implementation complete.
PR merged: [link]
Test results: All passing (X/Y)
Coverage: XX%
Security Guidelines
Never hardcode Jira API tokens in source code or skill filesAlways use environment variables or a secrets managerAdd .env to .gitignore in every projectRotate tokens immediately if exposed in git historyUse least-privilege API tokens scoped to required projectsValidate that credentials are set before making API calls — fail fast with a clear message
Troubleshooting Error Cause Fix 401 UnauthorizedInvalid or expired API token Regenerate at id.atlassian.com 403 ForbiddenToken lacks project permissions Check token scopes and project access 404 Not FoundWrong ticket key or base URL Verify JIRA_URL and ticket key spawn uvx ENOENTIDE cannot find uvx on PATH Use full path (e.g., ~/.local/bin/uvx) or set PATH in ~/.zprofile Connection timeout Network/VPN issue Check VPN connection and firewall rules
Best Practices
Update Jira as you go, not all at once at the end
Keep comments concise but informative
Link rather than copy — point to PRs, test reports, and dashboards
Use @mentions if you need input from others
Check linked issues to understand full feature scope before starting
If acceptance criteria are vague, ask for clarification before writing code
