SLA breached rules may not trigger if SLA ends exactly at end of day, or if threshold is less than 6 minutes

Issue Summary

SLA breached rules may not trigger if SLA ends exactly at end of day

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

Steps to re-produce:

1. Setup an SLA with a calendar (say 9-17:00)
2. Create an issue such that the SLA will breach exactly at 17:00
3. Create an automation rule with: SLA trigger with 'breached'
4. Add event (Then: Add comment to issue)

Now wait until 17:00. The SLA will be paused. Then the next day at 9AM it resumes (and is immediately breached - the rule should run now). However the automation rule doesn't run. This is due to timing inaccuracies around polling (most likely we never schedule the SLA trigger to check for breached SLA for this issue, since the SLA was already paused).

Expected Results

Once the SLA breaches, it should add a comment on the ticket.

Actual Results

Checking the Automation rule and SLA I can see that the SLA breached , Audit log shows SUCCESS, however the comment was not added.

Workaround

Use JSD automation for now