A4J - SLA threshold breached rule trigger may fail if threshold is lower than 6 minutes

Issue Summary

Automation for Jira allows you to configure a trigger based on an SLA breached threshold, it allows you to trigger a rule after X amount of time after the ticket has breached an SLA. However, if you specify a value of 5 minutes or less, it will fail intermittently.

This seems to be happening because A4J uses JQL calls to retrieve SLA breached data, however, these calls are being fired once in approx 5 minutes, so anything lower than this has the chance to not fire the rule.

Steps to Reproduce

1. Create a rule using the 'SLA breached threshold' trigger (example below)
   

Expected Results

• Automation for Jira triggers the role despite the low threshold value

Actual Results

• The rule won't be triggered all the times

Workaround

• Use the "Sla Breached" trigger or use a threshold higher than 5 minutes.