Issue Summary

SLA threshold breach automation rules are executed twice, with executions occurring exactly 4 minutes apart. This duplicate execution has the potential to cause data inconsistency and workflow disruption. Some examples of impact scenarios:

• Scenario 1 (Issue Transitions): When the automation performs an issue transition, the second execution attempt fails because the first execution has already transitioned the issue to the target status. This results in error logs and may trigger error notifications

• Scenario 2 (Work Logging): When the automation adds work logs, the duplicate execution creates two identical work log entries, leading to incorrect time tracking and inflated logged hours

Affected Versions

• Jira 10.3.19+
• Jira 11.3.3+

Steps to Reproduce

1. Configure a simple automation rule:
   • Create a new automation rule with an 'SLA threshold breached' trigger
   • Set the 'Trigger when SLA has' option to "breached"
2. Add actions:
   • Add 'Transition issue' action (configure target status)
   • Add 'Log work' action (configure time entry)
3. Trigger SLA breaches:
   • Create a few test issues that will breach their SLA thresholds
4. Monitor results:
   • Check the automation audit log for execution entries
   • Observe the following pattern:
     • First execution: SUCCESS status (rule executes correctly)
     • Second execution: Occurs exactly 4 minutes later with SOME_ERRORS status due to failed transition attempt and duplicate work log creation

Expected Results

Single execution per SLA breach.

Actual Results

Two executions occur exactly 4 minutes apart, with the second execution potentially failing depending on the configured rule actions.

In the automation audit log, the rule might fail, resulting the SOME_ERRORS status. 

Workaround

Change the SLA trigger configuration from "breached" to "breached by more than 5 minutes" to prevent duplicate executions.