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 JQL

What 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`

Fetch the ticket from Jira (via MCP jira_get_issue or 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-1234
Summary: [title]
Status: [status]
Priority: [priority]
Type: [Story/Bug/Task]
Requirements:
[extracted requirement]
[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 to implement with tests first

`/jira comment`

Summarize current session progress (what was built, tested, committed)
Format as a structured comment
Post to the Jira ticket

`/jira transition`

Fetch available transitions for the ticket
Show options to user
Execute the selected transition

`/jira search`

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:

# macOS/Linux
export JIRA_URL="https://yourorg.atlassian.net"
export JIRA_EMAIL="your.email@example.com"
export JIRA_API_TOKEN="your-api-token"

# Windows PowerShell
$env:JIRA_URL       = "https://yourorg.atlassian.net"
$env:JIRA_EMAIL     = "your.email@example.com"
$env:JIRA_API_TOKEN = "your-api-token"

Typing the token directly writes it to your shell history in plaintext, where it stays until the history file rolls over. Put it in a .env the shell sources (and that .gitignore covers), or read it from a secret manager:

export JIRA_API_TOKEN=$(op read "op://Private/Jira/token")   # 1Password
export JIRA_API_TOKEN=$(security find-generic-password -w -s jira)  # macOS Keychain

If credentials are missing, stop and direct the user to set them up.

Integration with Other Commands

After analyzing a ticket:

Use /plan to create an implementation plan from the requirements
Use /tdd to implement with test-driven development
Use /code-review after implementation
Use /jira comment to post progress back to the ticket
Use /jira transition to move the ticket when work is complete

Skill: skills/jira-integration/
MCP config: mcp-configs/mcp-servers.json → jira

/jira