Downtime Schedules cannot start in the past

Downtime Schedules cannot start in the past

If I create a Downtime Schedule that starts in the past, it will never take effect even if the ending date is in the future.. Here's an example:

1) I need to suppress alerts immediately and the time is currently 12:16 PM.
2) I create a Downtime Schedule for 12:15 PM to 18:00 PM.
3) I click the Update button to return the list of Schedules
4) The "Next Scheduled at" column says that it's Finished even though it should be in effect up through 18:00.

The only way to get around this is to select 12:30 PM as a starting time because we can only select times in 15 minute intervals. The problem is that now I have unnecessary alerts going out from 12:16 to 12:30 which adds unnecessary work for our support staff.

Is this behavior intentional?

                  New to ADSelfService Plus?