As a Systems Engineer responsible for PRTG alerting in an environment with scheduled maintenance windows,
I want to configure notification triggers so that an escalation trigger only activates if its preceding trigger has actually fired (and notifications were not paused at that time),
so that resuming notifications after maintenance does not cause immediate, unwarranted escalations, and my escalation chain always progresses step by step as designed.

Background:
We currently have maintenance windows during which certain sensors are allowed to remain Down for an extended period of time. During these windows, we only pause the notifications, while the sensors themselves are still shown as red (Down).
Because the sensor remains in a Down state, PRTG continues counting the Down duration in the background. Once the maintenance window ends and notifications are unpaused, higher‑level triggers (Trigger 2 and Trigger 3) may fire immediately, causing unwanted escalations.
Specifically, I want to be able to define:
- whether Trigger 2 only activates if Trigger 1 has fired,
- whether Trigger 3 only activates if Trigger 2 has fired.
Having configurable trigger dependencies would prevent this behavior and allow proper escalation control, especially in environments where sensors are intentionally Down during scheduled maintenance periods.