A4J - SLA threshold breached trigger will intermittently fail if the cycle is completed or paused

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 the SLA cycle has completed but still breached rule fails to trigger.

Steps to Reproduce

Quite hard to reproduce...

1. Setup an SLA that finishes when transitioned to a closed (or some other status)
2. Create a rule using the 'SLA breached threshold' trigger
   1. Triggers after 5 minutes of being breached
   2. Uses SLA in step 1
3. Trigger the SLA to breach on an issue
4. Wait roughly 4 minutes
5. Transition that issue to closed status

Expected Results

• The automation should run

Actual Results

• The automation will not run

Workaround

• No workaround