Example 5: Issue Is Not Started, and We Are Past "End Date" Minus "Estimated Hours", or Behind Schedule
The fifth example shows an escalation rule with a computed offset. We want to alert the issue's assignees, supervisors and the project admin, if an issue has not even started yet, and the remaining (work) time for the issue (until the scheduled completion date) falls below the estimated hours. This type of rule can be generalized escalation can be dependent on two or more fields and can be logically or arithmetically computed.
Figure: Escalation Behind Schedule Schematic
The escalation group predicate should select issues with Status not {Resolved, Closed} and Resolution unset.
Figure: Tracker Task Filter Behind Schedule
The escalation rule is anchored at the field End Date and the offset is retrieved from the field Estimated Hours.
Figure: Escalation Rule Behind Schedule
Both fields involved here, End Date and Estimated Hours are optional and mutable.
If either field value changes, the escalation is rescheduled.
If no End Date is specified for an issue, this escalation will be ignored. If no of Estimated Hours are specified, the escalation will be due at End Date.