Issue Summary

The behavior of the Due Date: Not Passed condition when it is used as a Paused condition in an SLA configuration is inconsistent.

Steps to Reproduce

1. In a Service Desk project, create an SLA configured to pause with the Due Date: Not Passed condition. Let's call this SLA "Due Date SLA"
2. Create a new issue with a not breached Due Date, and observe that the SLA "Due Date SLA" is paused
3. Let the Due Date breach naturally or force it by changing your date/time locally.
4. Refresh the issue created previously and observe that the SLA "Due Date SLA" is still paused

Expected Results

The behavior of an SLA pausing on the Due Date: Not Passed condition should be consistent when you let Due Date ages naturally.

Actual Results

The behavior of an SLA pausing on the Due Date: Not Passed condition is not consistent at all.

Workaround

There is no workaround for this at the moment.