How to Fix Jira Automation Rule Not Triggering

In this tutorial, you'll learn about How to Fix Jira Automation Rule Not Triggering. We cover key concepts, practical examples, and best practices.

Jira automation rules execute actions based on triggers (issue created, transitioned, or updated). When a rule does not trigger, the condition blocks execution, the project scope excludes the issue, or the rule is paused due to execution limits.

The Problem

You create an automation rule (e.g., "When a bug is created, assign to the default assignee") but nothing happens when you create the bug. The rule shows as "Active" but does not fire.

Wrong approach — deleting and recreating the same rule.

The Fix

Check the Audit log to see if the rule is being evaluated:

1. Jira Administration → Automation → Audit log
2. Find your rule in the list
3. Check the status: "Success," "Skipped," or "Error"
4. Click the entry to see why it was skipped

Common skip reasons and fixes:

"Condition failed" → Check rule conditions (e.g., issue type, status, project)
"Component error" → Check if referenced fields or values still exist
"Project scope excludes this issue" → Update scope to include the project

Check the rule scope:

1. Jira Administration → Automation → click the rule
2. Check "Project scope" — is it limited to specific projects?
3. Change to "All projects" or add the missing project

Expected output:

Rule triggers when the configured event occurs
Audit log shows "Success" for each trigger
Action (assign, transition, comment) executes correctly

Prevention Tips

• Always test automation rules with a real issue after creation
• Use the Audit log to debug rules that do not fire as expected
• Keep conditions minimal — each condition is a potential failure point
• Limit rule scope to specific projects when the rule is project-specific
• Monitor the Automation > "Rule errors" tab for recurring failures
• Set up email notifications for automation failures

Common Mistakes with automation rule

1. Using return to exit a function early instead of wrapping a pure value in the monad
2. Mixing let bindings with <- bindings in do notation, producing type errors
3. Overlapping type class instances that cause GHC to reject the program with ambiguous dispatch errors

These mistakes appear frequently in real-world JIRA code. DodaTech's contributors have identified these patterns through analysis of open-source projects and production systems.

Practice Exercise

Write a pure function that safely divides two integers using Maybe, then test it with edge cases like division by zero and negative numbers.

This exercise reinforces the concepts covered in this guide. Try implementing it before checking online solutions.

FAQ

Related: DodaTech's Automation Rule Debugger traces rule execution step by step, identifies failed conditions, and provides suggested fixes for common automation failures. Use with DodaZIP for rule backup.