Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
Atlassian Jira expert for creating and managing projects, planning, product discovery, JQL queries, workflows, custom fields, automation, reporting, and all Jira features. Use for Jira project setup, configuration, advanced search, dashboard creation, workflow design, and technical Jira operations.
domain
delivery
subdomain
delivery-tools
difficulty
intermediate
time-saved
TODO: Quantify time savings
frequency
TODO: Estimate usage frequency
use-cases
["Primary workflow for Jira Expert","Analysis and recommendations for jira expert tasks","Best practices implementation for jira expert","Integration with related skills and workflows"]
This skill provides comprehensive Jira expertise for project configuration, workflow design, advanced JQL queries, automation rules, custom fields, dashboards, and reporting. It covers all technical and operational aspects of Jira including Scrum/Kanban board setup, permission schemes, bulk operations, and integration with Confluence and external tools through the Atlassian MCP server.
Target users include Jira administrators, project managers, Scrum Masters, technical leads, and agile coaches who need to configure projects, optimize workflows, create advanced filters and dashboards, or automate Jira operations. This skill is essential for teams setting up new Jira projects, customizing workflows, implementing automation, or generating portfolio-level reports.
Core Value: Reduce project setup time by 60% through templates and automation, improve team productivity by 35% through optimized workflows and JQL filters, and increase reporting efficiency by 70% through custom dashboards and automated data extraction.
Core Capabilities
Project Configuration & Workflows - Create and configure Jira projects (Scrum, Kanban, custom) with custom workflows, issue types, fields, screens, and permission schemes
JQL Mastery & Advanced Queries - Write complex JQL queries for any use case, build saved filters with multiple conditions, optimize query performance, and create team-specific views
Automation & Integration - Design Jira automation rules, configure webhooks, set up email notifications, and integrate with external tools (Confluence, Slack, CI/CD)
Dashboards & Reporting - Create custom dashboards with gadgets, build reports for sprint metrics, velocity, burndown, configure portfolio-level reporting, and export data for executive visibility
Atlassian MCP Integration - Direct Jira operations via MCP server for project creation, JQL execution, issue updates, sprint management, report generation, and workflow configuration
Quick Start
Common Jira Operations
This skill provides Jira expertise through knowledge frameworks, JQL patterns, and workflow templates. Actual Jira operations are performed through the Atlassian MCP server configured in Claude Code settings.
Access Documentation Resources
JQL reference: See JQL Query Building section for operators, functions, and powerful query examples
Workflow patterns: See Workflow Design section for workflow configuration and transition setup
Automation examples: See Automation Rules section for trigger, condition, and action patterns
See Dashboard Creation section for gadget configuration and layout patterns
Dashboard templates:
Key Workflows to Start With
Configure New Scrum Project - Set up a new Jira project with workflow, permissions, and board (1.5 hours)
Build Advanced Dashboard for Reporting - Create executive dashboard with key metrics and JQL filters (1 hour)
Create Automation Rules for Team Efficiency - Implement automation to reduce manual work (1 hour)
Master JQL for Complex Queries - Build advanced queries for filtering, reporting, and bulk operations (varies)
Key Workflows
1. Configure New Scrum Project
Time: 1.5 hours
Steps:
Create Jira project - Go to Projects → Create project → Select Scrum template
Configure issue types - Customize the issue types for your workflow
Epic: Large features/initiatives
Story: User-facing feature work
Task: Non-user-facing work
Bug: Defect reports
Subtask: Breakdown complex stories
Optional: Add custom types (e.g., "Spike" for research)
Create workflow schema - Design workflow states and transitions
To Do → In Progress → In Review → Done
- To Do: Initial state for all issues
- In Progress: Active development
- In Review: Awaiting code/design review
- Done: Complete and merged/deployed
Define who can transition between states
Add validators (required fields before transition)
Add post-functions (auto-assign, notify watchers)
Set up project permissions - Configure who can browse, create, and manage issues
Developers: Create/Edit/Transition issues
QA: Create bugs, view all issues
PM: Admin access
Stakeholders: View-only
Configure board and backlog - Set up Scrum board for sprint management
Enable columns for each workflow state
Configure backlog visibility
Set default issue view
Create board filters and saved searches - Set up standard queries for team use
My Issues: assignee = currentUser() AND status != Done
Blocked: issuekey in linkedIssues(PROJ, "is blocked by")
Ready for Dev: priority >= High AND status = "To Do"
Expected Output: Fully configured Scrum project ready for team to begin working. Team can create stories, manage sprints, and track progress with consistent workflow and permissions.
Add velocity chart gadget - Tracks story points completed per sprint
Use last 10 sprints
Shows team capacity trends
Helps forecast future sprint capacity
Add created vs resolved gadget - Shows issue intake vs completion rate
Monitors if backlog is growing/shrinking
Use 30-day timeframe
Add filter results gadget - Custom issue list using JQL
# High priority bugs
type = Bug AND priority = High AND status != Done
Add separate gadget for high priority issues
Add gadget for overdue issues
Arrange and share dashboard - Position gadgets for readability
Executive summary at top
Detailed metrics below
Share with stakeholders
Expected Output: Live dashboard providing real-time view into team metrics, sprint health, and backlog status. Stakeholders can monitor progress without asking for updates.
Choose fields to update (e.g., Fix Version, Epic Link, Labels)
Preview changes before executing
Execute bulk operation
Verify migration success - Check sample of updated issues
Spot check 10-20 updated issues
Verify fields updated correctly
Check that no data was lost
Update affected reports and dashboards - Refresh any dashboards or filters
Rerun velocity reports
Update any hardcoded issue lists
Notify team of changes
Document changes - Create audit trail
Record what was changed
Why the change was made
Date and who performed it
Expected Output: Data cleanup completed successfully with verified accuracy. Old or incorrect data is corrected, and audit trail is documented for compliance/reference.
See Bulk Operations section for detailed operation procedures.
Python Tools
This skill does not include Python automation tools. Jira operations are performed directly through the Atlassian MCP server, which provides native integration for:
Creating and configuring projects
Executing JQL queries for data extraction
Updating issue fields and statuses
Creating and managing sprints
Generating reports and dashboards
Configuring workflows and automation
Managing boards and filters
See the Atlassian MCP Integration section below for detailed integration patterns and capabilities.
Reference Documentation
The following sections provide comprehensive frameworks, JQL patterns, and best practices for Jira expertise:
Core Competencies
Project Configuration
Create and configure Jira projects (Scrum, Kanban, custom)
Design and implement custom workflows
Configure issue types, fields, and screens
Set up project permissions and security schemes
JQL Mastery
Write advanced JQL queries for any use case
Create complex filters with multiple conditions
Optimize query performance
Build saved filters for team use
Automation & Integration
Design Jira automation rules
Configure webhooks and integrations
Set up email notifications
Integrate with external tools (Confluence, Slack, etc.)
Reporting & Dashboards
Create custom dashboards with gadgets
Build reports for sprint metrics, velocity, burndown
Configure portfolio-level reporting
Export data for executive reporting
Workflows
Project Creation
Determine project type (Scrum, Kanban, Bug Tracking, etc.)
Create project with appropriate template
Configure project settings:
Name, key, description
Project lead and default assignee
Notification scheme
Permission scheme
Set up issue types and workflows
Configure custom fields if needed
Create initial board/backlog view
HANDOFF TO: Scrum Master for team onboarding
Workflow Design
Map out process states (To Do → In Progress → Done)
Define transitions and conditions
Add validators, post-functions, and conditions
Configure workflow scheme
Associate workflow with project
Test workflow with sample issues
USE: References for complex workflow patterns
JQL Query Building
Basic Structure: field operator value
Common Operators:
=, != : equals, not equals
~, !~ : contains, not contains
>, <, >=, <= : comparison
in, not in : list membership
is empty, is not empty
was, was in, was not
changed
Powerful JQL Examples:
Find overdue issues:
dueDate < now() AND status != Done
Sprint burndown issues:
sprint = 23 AND status changed TO "Done" DURING (startOfSprint(), endOfSprint())
Find stale issues:
updated < -30d AND status != Done
Cross-project epic tracking:
"Epic Link" = PROJ-123 ORDER BY rank
Velocity calculation:
sprint in closedSprints() AND resolution = Done
Team capacity:
assignee in (user1, user2) AND sprint in openSprints()
Dashboard Creation
Create new dashboard (personal or shared)
Add relevant gadgets:
Filter Results (JQL-based)
Sprint Burndown
Velocity Chart
Created vs Resolved
Pie Chart (status distribution)
Arrange layout for readability
Configure automatic refresh
Share with appropriate teams
HANDOFF TO: Senior PM or Scrum Master for use
Automation Rules
Define trigger (issue created, field changed, scheduled)
Add conditions (if applicable)
Define actions:
Update field
Send notification
Create subtask
Transition issue
Post comment
Test automation with sample data
Enable and monitor
USE: References for complex automation patterns
Advanced Features
Custom Fields
When to Create:
Track data not in standard fields
Capture process-specific information
Enable advanced reporting
Field Types:
Text: Short text, paragraph
Numeric: Number, decimal
Date: Date picker, date-time
Select: Single select, multi-select, cascading
User: User picker, multi-user picker
Configuration:
Create custom field
Configure field context (which projects/issue types)
Add to appropriate screens
Update search templates if needed
Issue Linking
Link Types:
Blocks / Is blocked by
Relates to
Duplicates / Is duplicated by
Clones / Is cloned by
Epic-Story relationship
Best Practices:
Use Epic linking for feature grouping
Use blocking links to show dependencies
Document link reasons in comments
Permissions & Security
Permission Schemes:
Browse Projects
Create/Edit/Delete Issues
Administer Projects
Manage Sprints
Security Levels:
Define confidential issue visibility
Control access to sensitive data
Audit security changes
Bulk Operations
Bulk Change:
Use JQL to find target issues
Select bulk change operation
Choose fields to update
Preview changes
Execute and confirm
Monitor background task
Bulk Transitions:
Move multiple issues through workflow
Useful for sprint cleanup
Requires appropriate permissions
JQL Functions Reference
Date Functions:
startOfDay(), endOfDay()
startOfWeek(), endOfWeek()
startOfMonth(), endOfMonth()
startOfYear(), endOfYear()
Sprint Functions:
openSprints()
closedSprints()
futureSprints()
User Functions:
currentUser()
membersOf("group")
Advanced Functions:
issueHistory()
linkedIssues()
issuesWithFixVersions()
Reporting Templates
Sprint Report:
project = PROJ AND sprint = 23
Team Velocity:
assignee in (team) AND sprint in closedSprints() AND resolution = Done
