jira-automationlisted

# Jira Automation > **Configure:** Set the project keys, components, labels, team roster, and Jira instance URL for your organization in your project context (CLAUDE.md or local profile). Patterns below are organization-agnostic. ## Purpose Automate Jira workflows for Product & Engineering teams. Create properly formatted Epics, Design Stories, and Implementation Stories following team conventions. Run JQL queries, manage sprints, and handle bulk operations — all via Atlassian MCP without leaving Claude Code. ## When to Use - **Ticket creation:** "Create a Jira ticket for [feature]" / "Break down this PRD into tickets" - **Bulk operations:** "Create all the stories for this Epic" / "Update these tickets" - **JQL queries:** "Find stale tickets" / "Show me unassigned work in the sprint" - **Sprint management:** "Move these to Sprint 24" / "Sprint health check" - **Templates:** "Create a Design story for [feature]" / "Write an Implementation ticket" ## Jira Configuration (set per project) ### Instance - **URL:** `https://<your-instance>.atlassian.net` - **Browse:** `https://<your-instance>.atlassian.net/browse/` ### Project Keys (configure) | Key | Name | Use | |-----|------|-----| | **<PROJECT_KEY>** | Primary P&E project | Most tickets go here (set as default) | | **<SECONDARY_KEY>** | Secondary P&E project | Cross-team work | | **<CONTENT_KEY>** | Content/marketing | Editorial / CMS | | **<DESIGN_KEY>** | Design | Design requests | | **<DATA_KEY>** | Data Engineerin