jira
Retrieve a Jira ticket, analyze requirements, update status, or add comments. Uses the jira-integration skill and MCP or REST API.
Jira Command
Interact with Jira tickets directly from your workflow — fetch tickets, analyze requirements, add comments, and transition status.
Usage
/jira get <TICKET-KEY> # Fetch and analyze a ticket/jira comment <TICKET-KEY> # Add a progress comment/jira transition <TICKET-KEY> # Change ticket status/jira search <JQL> # Search issues with JQLWhat This Command Does
- Get & Analyze — Fetch a Jira ticket and extract requirements, acceptance criteria, test scenarios, and dependencies
- Comment — Add structured progress updates to a ticket
- Transition — Move a ticket through workflow states (To Do → In Progress → Done)
- Search — Find issues using JQL queries
How It Works
/jira get <TICKET-KEY>
- Fetch the ticket from Jira (via MCP
jira_get_issueor REST API) - Extract all fields: summary, description, acceptance criteria, priority, labels, linked issues
- Optionally fetch comments for additional context
- Produce a structured analysis:
Ticket: PROJ-1234Summary: [title]Status: [status]Priority: [priority]Type: [Story/Bug/Task]
Requirements:1. [extracted requirement]2. [extracted requirement]
Acceptance Criteria:- [ ] [criterion from ticket]
Test Scenarios:- Happy Path: [description]- Error Case: [description]- Edge Case: [description]
Dependencies:- [linked issues, APIs, services]
Recommended Next Steps:- /plan to create implementation plan- `tdd-workflow` skill to implement with tests first/jira comment <TICKET-KEY>
- Summarize current session progress (what was built, tested, committed)
- Format as a structured comment
- Post to the Jira ticket
/jira transition <TICKET-KEY>
- Fetch available transitions for the ticket
- Show options to user
- Execute the selected transition
/jira search <JQL>
- Execute the JQL query against Jira
- Return a summary table of matching issues
Prerequisites
This command requires Jira credentials. Choose one:
Option A — MCP Server (recommended):
Add jira to your mcpServers config (see mcp-configs/mcp-servers.json for the template).
Option B — Environment variables:
export JIRA_URL="https://yourorg.atlassian.net"export JIRA_EMAIL="your.email@example.com"export JIRA_API_TOKEN="your-api-token"If credentials are missing, stop and direct the user to set them up.
Integration with Other Commands
After analyzing a ticket:
- Use
/planto create an implementation plan from the requirements - Use the
tdd-workflowskill to implement with test-driven development - Use
/code-reviewafter implementation - Use
/jira commentto post progress back to the ticket - Use
/jira transitionto move the ticket when work is complete
Related
- Skill:
skills/jira-integration/ - MCP config:
mcp-configs/mcp-servers.json→jira