Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
Fetches and analyzes Jira tickets, adds structured comments, transitions status, or searches issues with JQL. Produces requirement breakdowns, test scenarios, and summaries.
npx claudepluginhub littlebearbond/everything-claude-codeHow this command is triggered — by the user, by Claude, or both
Slash command
/everything-claude-code:jiraFiles this command reads when invoked
The summary Claude sees in its command listing — used to decide when to auto-load this command
# Jira Command Interact with Jira tickets directly from your workflow — fetch tickets, analyze requirements, add comments, and transition status. ## Usage ## What This Command Does 1. **Get & Analyze** — Fetch a Jira ticket and extract requirements, acceptance criteria, test scenarios, and dependencies 2. **Comment** — Add structured progress updates to a ticket 3. **Transition** — Move a ticket through workflow states (To Do → In Progress → Done) 4. **Search** — Find issues using JQL queries ## How It Works ### `/jira get <TICKET-KEY>` 1. Fetch the ticket from Jira (via MCP `jira_...
/jiraManages Jira tickets: fetch and analyze requirements, add comments, transition status, or search issues with JQL.
/jiraInteracts with Jira tickets — fetches and analyzes tickets, adds comments, transitions status, and searches via JQL.
/qa-reviewReviews JIRA tickets in QA status: improves descriptions, creates/updates Confluence docs, responds to comments. Generates summary report with quality stats, links, and auto-logs time.
/execute-ticketExecutes a Jira ticket by fetching its implementation plan, exploring codebase, and running steps. Supports parallel execution with specialized agents.
/f5-jiraManages unified Jira integration: setup connection, sync issues/files, check status, convert Excel/CSV, handle issues/attachments via subcommands.
Share bugs, ideas, or general feedback.
Interact with Jira tickets directly from your workflow — fetch tickets, analyze requirements, add comments, and transition status.
/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
/jira get <TICKET-KEY>jira_get_issue or REST API)Ticket: PROJ-1234
Summary: [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 to implement with tests first
/jira comment <TICKET-KEY>/jira transition <TICKET-KEY>/jira search <JQL>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.
After analyzing a ticket:
/plan to create an implementation plan from the requirements/tdd to implement with test-driven development/code-review after implementation/jira comment to post progress back to the ticket/jira transition to move the ticket when work is completeskills/jira-integration/mcp-configs/mcp-servers.json → jira