Jira Automation Rules: The Complete Guide for 2026

What Is Jira Automation?

Jira Automation (formerly Automation for Jira) is a built-in, no-code rules engine that lets you automate repetitive actions in Jira. It's available on all Jira Cloud plans — including Free — and can save engineering teams hours of manual work every week.

Every automation rule has three parts: a trigger (what starts the rule), optional conditions (when to run it), and actions (what to do). Once you understand that structure, you can automate almost any Jira workflow.

Getting Started: Where to Find Automation

In Jira Cloud: go to your Project Settings → Automation for project-level rules, or Settings → System → Automation (requires admin) for global rules that run across all projects.

The 10 Most Useful Jira Automation Rules

1. Auto-Assign Issues Based on Component

When issues are created with a specific component, automatically assign them to the right person.

Trigger: Issue created

Condition: Component = "Backend API"

Action: Assign issue to [backend lead]

This eliminates the triage step for clear-cut issues and ensures nothing sits unassigned.

2. Auto-Close Resolved Issues After 7 Days

Issues sitting in "Resolved" status clog up boards. Auto-close them.

Trigger: Scheduled — daily at 9am

Condition: Status = Resolved AND Status category changed more than 7 days ago

Action: Transition issue to Done

3. Notify Slack When a Bug Is Marked Critical

Get instant Slack notifications for high-priority issues without anyone having to remember to post.

Trigger: Issue updated

Condition: Priority changed to Critical OR Blocker

Action: Send web request (POST to Slack webhook URL)

{
  "text": "🚨 Critical bug created: {{issue.summary}}\nAssignee: {{issue.assignee.displayName}}\nLink: {{issue.url}}"
}

4. Sync Parent Epic Status With Child Issues

Automatically move an Epic to "In Progress" when any of its child stories start.

Trigger: Issue transitioned

Condition: Issue type = Story AND Status = In Progress

Action: Edit parent issue — set Status to In Progress

5. Add a Comment When SLA Is Breached

For teams using Jira Service Management, alert the assignee when a ticket is about to breach SLA.

Trigger: SLA breached (or approaching breach)

Action: Add comment — "@{{issue.assignee}} this ticket is approaching SLA breach. Please update or escalate."

Action: Assign issue to [escalation team]

6. Auto-Label Issues From Summary Keywords

Issues containing words like "login", "auth", or "password" in their title get auto-labelled "security" for easy filtering.

Trigger: Issue created

Condition: Summary contains "login" OR "auth" OR "password" OR "token"

Action: Edit issue — add label "security"

7. Clone Issues to Another Project

When a story is moved to a specific status, clone it to a separate QA or release project.

Trigger: Issue transitioned to "Ready for QA"

Action: Clone issue to project "QA Tracking"

Action: Link issues — "is tested by"

8. Set Due Date Automatically Based on Priority

Remove the manual step of setting due dates by calculating them from priority at creation time.

Trigger: Issue created

Condition: Priority = High

Action: Edit issue — set Due date to {{now.plusDays(3)}}

For Medium priority: {{now.plusDays(7)}}. For Low: {{now.plusDays(14)}}.

9. Send a Weekly Summary Email to the Team

Every Monday morning, email the team lead a summary of open issues by priority.

Trigger: Scheduled — every Monday at 8am

Action: Send email to [team lead email]

Subject: Weekly Jira Summary — {{project.name}}

Open issues by priority:
- Critical: {{issues.where(priority = Critical).size}}
- High: {{issues.where(priority = High).size}}
- Medium: {{issues.where(priority = Medium).size}}

Issues added this week: {{issues.where(created >= startOfWeek()).size}}

10. Re-Open Issues When a Linked Pull Request Fails CI

When a linked GitHub/Bitbucket PR fails its build, automatically re-open the Jira issue.

Trigger: Pull request status changed

Condition: Pull request status = Failed

Action: Transition linked issue to "In Progress"

Action: Add comment — "CI failed on linked PR. Reopening for investigation."

Smart Values: The Power Feature Most Teams Miss

Smart values are Jira Automation's variable system — they let you reference issue data dynamically. Written inside {{ }} double curly braces.

Most Useful Smart Values

String Manipulation

{{issue.summary.toUpperCase()}}         → ISSUE TITLE IN CAPS
{{issue.summary.substring(0, 50)}}      → First 50 characters
{{issue.summary.replace("bug", "fix")}} → Replace text

Conditions: Keeping Rules From Firing When They Shouldn't

Without conditions, automation rules can fire at the wrong time and cause chaos. Always add conditions to scope your rules precisely.

Useful Condition Types

Issue fields condition: Check any field value — "Priority equals High", "Component contains Backend", "Reporter is in group developers"

JQL condition: Write a full JQL query to check if the issue matches. Most flexible option.

project = "MYAPP" AND issuetype = Bug AND priority in (Critical, High)

Branch condition: Inside a "For each" loop, filter which items get acted on.

User condition: Only run if the person who triggered the event is (or isn't) in a specific group. Useful for preventing automation from triggering on changes made by other automations.

Common Automation Mistakes to Avoid

Mistake 1: Automation loops — Rule A triggers Rule B which triggers Rule A. Always check if your rule could trigger itself. Use the "If the rule is a re-run, skip it" option or add a condition checking the actor is not the Automation actor.

Mistake 2: No audit logging — Always check the Automation audit log (available in the Automation screen) before assuming a rule worked. It shows every rule execution, success, and failure with full details.

Mistake 3: Global rules that run on too many issues — A global scheduled rule running every hour across 10,000 issues can hit Jira's automation execution limits. Scope global rules as tightly as possible with JQL conditions.

Mistake 4: Not testing in a staging project first — Test new rules in a sandbox project before enabling them on production. One bad rule can spam hundreds of comments or mis-transition thousands of issues.

Automation Limits by Plan

If you're on Standard and hitting limits, audit your rules for ones firing too frequently or on too many issues. Scheduled rules that run hourly are often the culprit.

Need Help Building Custom Jira Automation?

We design and implement Jira Automation rule sets for engineering teams — from simple auto-assignment to complex cross-project workflows with Slack integrations and CI/CD hooks.

Talk to a Jira automation specialist →