Disclosure: Some links below are affiliate links. If you buy through them, we may earn a commission at no extra cost to you. Full disclosure. We only recommend tools we have tested.
Jira automation rules are one of the most underused features in Atlassian’s project management platform. Teams that master automation save hours every sprint by eliminating repetitive manual tasks — from reassigning issues to closing resolved tickets automatically. In this guide, we cover the 10 best Jira automation rules you can activate today.
1. Auto-Assign Issues Based on Component
When a new issue is created and tagged with a specific component (e.g., “Backend,” “Design,” or “QA”), Jira can automatically assign it to the right team member or lead. This eliminates the daily triaging session where a project manager manually routes new tickets.
How to set it up: Trigger = “Issue created” → Condition = “Component equals [Component Name]” → Action = “Assign to [Team Lead].” Save and activate. Most teams see 40–60% fewer unassigned issues within the first week.
2. Send Slack Notification When Priority Changes to Highest
When any issue is escalated to “Highest” priority, your team needs to know immediately. A Jira automation rule can send a direct Slack message (or Microsoft Teams notification) the moment a priority change is detected — no manual @mentions needed.
Trigger: “Field value changed” (Priority → Highest) → Action: “Send web request” to your Slack webhook URL with a custom message payload. You can include dynamic variables like {{issue.summary}} and {{issue.assignee}} for full context.
3. Transition Issues Automatically When All Sub-Tasks Are Done
Parent issues often linger in “In Progress” long after all sub-tasks have been resolved because no one remembers to move the parent. This rule watches sub-tasks and transitions the parent story to “Done” automatically once every child is complete.
Trigger: “Issue transitioned” (sub-task → Done) → Condition: “All sub-tasks are done” → Action: “Transition parent issue to Done.” This is one of the highest-ROI rules for Scrum teams running story-based sprints.
4. Auto-Close Stale Issues Inactive for 30+ Days
Backlog rot is a real problem. Issues that haven’t been updated in 30 days are often irrelevant or superseded. An automation rule can flag and eventually close these tickets, keeping your backlog clean and your velocity metrics accurate.
Setup: Trigger = “Scheduled” (runs daily) → Condition = “Issue has not been updated in 30 days AND status = Open” → Action = “Add comment: This issue is being closed due to inactivity. Reopen if still relevant.” → Action = “Transition to Closed.” Add a 7-day warning comment rule before the final close for a two-step process.
5. Re-Open Issues When a Customer Replies
In service desk and support workflows, a resolved issue should automatically re-open if the customer responds. Without automation, these replies get missed and customers feel ignored. This single rule can dramatically improve your CSAT scores.
Trigger: “Comment added” → Condition: “Comment author is a customer (non-team member)” AND “Issue status = Resolved” → Action: “Transition to In Progress” AND “Assign to Reporter’s organization’s service agent.”
6. Sync Epic Status to Its Stories
When a product manager moves an epic to “In Progress,” it’s usually because at least one story under it has started. Rather than manually updating all related stories, a sync rule propagates status changes down the hierarchy automatically.
Trigger: “Issue transitioned” (Epic → In Progress) → Action: “Transition all linked stories to In Progress.” Combine this with Rule #3 (sub-task completion) for a fully automated epic-to-story pipeline that reflects real team progress.
7. Set Due Dates Automatically Based on Priority
Enforcing SLAs is far easier when due dates are set automatically at the moment of issue creation. High priority issues get a 24-hour SLA; medium priority get 72 hours; low priority get 7 days. No more manual date-setting or missed deadlines.
Trigger: “Issue created” → Branch by priority: Highest/High → set due date to {{now.plusHours(24)}}; Medium → {{now.plusDays(3)}}; Low → {{now.plusDays(7)}}. Use Jira’s smart values ({{…}}) for dynamic date calculation.
8. Label Issues Based on Keywords in the Summary
Auto-tagging issues based on keywords in the title saves enormous time in triage. If a summary contains “login” or “auth,” apply the “Authentication” label. If it contains “payment” or “checkout,” apply “Revenue-Critical.” This helps with filtering and reporting instantly.
Trigger: “Issue created” → Condition: “Summary matches regex (?i)(login|auth|password)” → Action: “Add label: Authentication.” Create one rule per keyword group. This combines well with Rule #1 (auto-assign) to fully route new issues hands-free.
9. Post a Daily Stand-Up Digest to Slack
Replace your manual stand-up update with an automated daily digest. Every morning at 9 AM, Jira can post a summary of all issues in “In Progress” per team member directly to your Slack channel. Your stand-up becomes a 5-minute exception review instead of a 30-minute status read-out.
Trigger: “Scheduled” (9:00 AM Monday–Friday) → Action: “Send web request” to Slack webhook with a JQL-filtered list: {{issues.with(status = “In Progress” AND assignee in membersOfRole(“Software Developer”))}}. Each team member sees their own issues highlighted.
10. Auto-Transition Issues to “In Review” When a PR Is Opened
With Jira’s GitHub/Bitbucket/GitLab integration, you can trigger workflow transitions based on pull request events. When a developer opens a PR referencing a Jira issue key (e.g., “PROJ-123”), the issue automatically moves from “In Progress” to “In Review” — no manual update needed.
Trigger: “Pull request opened” (via Dev Tools integration) → Condition: “Issue linked to PR” → Action: “Transition to In Review.” Combine with a PR-merged trigger to move to “Done” and a PR-closed-without-merge trigger to move back to “In Progress.”
Jira Automation Rules: Plan Limits Comparison
Before setting up automation, know your plan’s rule-run allowances:
| Plan | Rule Runs/Month | Scope | Multi-Project |
|---|---|---|---|
| Free | 100 per project | Single project | No |
| Standard | 1,700 global | Global | Yes |
| Premium | Unlimited | Global | Yes |
| Enterprise | Unlimited | Global + multi-site | Yes |
Frequently Asked Questions
What are Jira automation rules?
Jira automation rules are trigger-action sequences that automatically perform tasks like assigning issues, sending notifications, or transitioning statuses when specific events occur. They save teams hours of manual project management work every sprint.
How many automation rules can I have in Jira?
You can create unlimited rules on all plans. The limit is on rule runs (executions): Free plans allow 100 runs/month per project, Standard allows 1,700 global runs/month, and Premium offers unlimited runs. There is no cap on the number of rules you create.
Can Jira automation rules span multiple projects?
Yes, on Jira Standard and above. Global automation rules can monitor events across multiple projects simultaneously, making them ideal for cross-functional teams working on related epics in different project spaces.
Start Automating Your Jira Workflows Today
These 10 Jira automation rules are all available on the Standard plan and above. Start with Rules 1, 3, and 10 for the highest immediate ROI — they address the three biggest sources of manual work for most engineering teams. Once active, you’ll wonder how you ever managed sprints without them.
Looking to go deeper? Check out our guides on AI automation for business and the best automation software platforms for 2026.
Further Reading
- Atlassian Jira Automation Template Library — Official template library with 100+ pre-built automation rules you can activate in one click.
- Atlassian Blog: Jira Automation Best Practices — Tips and case studies on how teams use automation to save hours per sprint.
- Zapier: Best Jira Integrations for 2026 — How to extend Jira automation to 500+ external tools via Zapier workflows.
Related Articles
