Recurring Downtime | Define by Time Ranges (Downtime is DST aware)

We would like to be able to define recurring downtime in terms of time ranges (e.g. 22:00 - 00:00) in additional to absolute terms periods (e.g. 2 hours).

This is possible for Scheduled Downtime for hosts / services, but it's not feasible to configure bulk downtimes in this manner

The motivation for this change is to ensure that downtimes are DST aware.

We noticed that during the change from Summer to Winter time that downtimes set during the DST period, services emerged from the downtime an hour earlier than users were expecting. For example a downtime of 48 hour duration from Friday 00:00 to Sunday 00:00 emerged from downtime on 23:00 on Sunday during DST.

Although this was correct - the elapsed duration was for a cumulative 48 hours - the user experience was counter-intuitive. A more natural configuration would be define downtimes by their start and end time; this would have avoided the issue that occurred during the DST change.