SLA threshold breached Trigger Misfires

Issue Summary

If we set the "SLA threshold breached" trigger to "will breach in the next 5 Days," it will actually fire five (5) days after the SLA starts counting down, rather than five days until the SLA is breached.

Steps to Reproduce

1. Create a JSM project
2. Create an automation using the "SLA threshold breached" trigger
   1. Use the default Time to Resolution SLA with the sample 9-5 calendar
   2. Select "will breach in the next" and set this to "5" and "days"
   3. Select any Action (e.g., send an email or add to the audit log)
3. Create an issue that falls under the selected SLA 
    
4. Note when the issue is due to breach and when the Action is triggered.

Expected Results

The automation will be triggered five days before the SLA is breached.

Actual Results

The automation is triggered five days after the SLA starts counting down.

Workaround

It seems that using hours (e.g., 40 hours, assuming nine (9) hour workdays) gets past this limitation.