
Jira Expert
Copy and adapt Jira automation rule patterns for auto-assignment, parent–subtask status sync, and Slack alerts when you run tickets alongside your agent.
Install
npx skills add https://github.com/alirezarezvani/claude-skills --skill jira-expertWhat is this skill?
- Auto-assign by component lead, reporter on feedback, and round-robin for unassigned ABC-project issues
- Parent/subtask status sync when all subtasks finish or when a parent is cancelled
- Epic progress comments and custom-field updates when linked issues reach Done
- High-priority bug Slack notifications to #engineering with structured template
Adoption & trust: 662 installs on skills.sh; 17.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
Recommended Skills
Agent Browservercel-labs/agent-browser
Lark Imlarksuite/cli
Lark Calendarlarksuite/cli
Lark Sheetslarksuite/cli
Lark Vclarksuite/cli
Lark Contactlarksuite/cli
Journey fit
Common Questions / FAQ
Is Jira Expert safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.
SKILL.md
READMESKILL.md - Jira Expert
# Jira Automation Examples ## Auto-Assignment Rules ### Auto-assign by component **Trigger:** Issue created **Conditions:** - Component is not EMPTY **Actions:** - Assign issue to component lead ### Auto-assign to reporter for feedback **Trigger:** Issue transitioned to "Waiting for Feedback" **Actions:** - Assign issue to reporter - Add comment: "Please provide additional information" ### Round-robin assignment **Trigger:** Issue created **Conditions:** - Project = ABC - Assignee is EMPTY **Actions:** - Assign to next team member in rotation (use smart value) --- ## Status Sync Rules ### Sync subtask status to parent **Trigger:** Issue transitioned **Conditions:** - Issue type = Sub-task - Transition is to "Done" - Parent issue exists - All subtasks are Done **Actions:** - Transition parent issue to "Done" ### Sync parent to subtasks **Trigger:** Issue transitioned **Conditions:** - Issue type has subtasks - Transition is to "Cancelled" **Actions:** - For each: Sub-tasks - Transition issue to "Cancelled" ### Epic progress tracking **Trigger:** Issue transitioned **Conditions:** - Epic link is not EMPTY - Transition is to "Done" **Actions:** - Add comment to epic: "{{issue.key}} completed" - Update epic custom field "Progress" --- ## Notification Rules ### Slack notification for high-priority bugs **Trigger:** Issue created **Conditions:** - Issue type = Bug - Priority IN (Highest, High) **Actions:** - Send Slack message to #engineering: ``` 🚨 High Priority Bug Created {{issue.key}}: {{issue.summary}} Reporter: {{issue.reporter.displayName}} Priority: {{issue.priority.name}} {{issue.url}} ``` ### Email assignee when mentioned **Trigger:** Issue commented **Conditions:** - Comment contains @mention of assignee **Actions:** - Send email to {{issue.assignee.emailAddress}}: ``` Subject: You were mentioned in {{issue.key}} Body: {{comment.author.displayName}} mentioned you: {{comment.body}} ``` ### SLA breach warning **Trigger:** Scheduled - Every hour **Conditions:** - Status != Done - SLA time remaining < 2 hours **Actions:** - Send email to {{issue.assignee}} - Add comment: "⚠️ SLA expires in <2 hours" - Set priority to Highest --- ## Field Automation Rules ### Auto-set due date **Trigger:** Issue created **Conditions:** - Issue type = Bug - Priority = Highest **Actions:** - Set due date to {{now.plusDays(1)}} ### Clear assignee when in backlog **Trigger:** Issue transitioned **Conditions:** - Transition is to "Backlog" - Assignee is not EMPTY **Actions:** - Assign issue to Unassigned - Add comment: "Returned to backlog, assignee cleared" ### Auto-populate sprint field **Trigger:** Issue transitioned **Conditions:** - Transition is to "In Progress" - Sprint is EMPTY **Actions:** - Add issue to current sprint ### Set fix version based on component **Trigger:** Issue created **Conditions:** - Component = "Mobile App" **Actions:** - Set fix version to "Mobile v2.0" --- ## Escalation Rules ### Auto-escalate stale issues **Trigger:** Scheduled - Daily at 9:00 AM **Conditions:** - Status = "Waiting for Response" - Updated < -7 days **Actions:** - Add comment: "@{{issue.reporter}} This issue needs attention" - Send email to project lead - Add label: "needs-attention" ### Escalate overdue critical issues **Trigger:** Scheduled - Every hour **Conditions:** - Priority IN (Highest, High) - Due date < now() - Status != Done **Actions:** - Transition to "Escalated" - Assign to project manager - Send Slack notification ### Auto-close inactive issues **Trigger:** Scheduled - Daily at 10:00 AM **Conditions:** - Status = "Waiting for Customer" - Updated < -30 days **Actions:** - Transition to "Closed" - Add comment: "Auto-closed due to inactivity" - Send email to reporter --- ## Sprint Automation Rules ### Move incomplete work to next sprint **Trigger:** Sprint closed **Conditions:** - Issue status != Done **Actions:** - Add issue to next sprint - Add comment: "Moved from {{sprint.name}}" #