Managing the schedule exceptions

<p><strong>Schedules and escalations are out of the beta</strong> After a two month beta period, on-call schedules, rotations and escalations features have come out of beta and available to all Pro and Enterprise level subscribers. Several usability improvements have been rolled out based on the feedback we&#8217;ve received during the beta process. Thanks for all the feedback! <strong>Great, but can we handle schedule exceptions?</strong> As expected, the most common enhancement request related to schedules was handling of the exceptions, when a user is not available to participate in on-call schedule rotation for whatever reason. In OpsGenie, a user may receive alert notifications for number of reasons, due to being part of a group, an escalation chain, a schedule etc.. We&#8217;ve quickly concluded that defining exceptions for each of these separately would be a burden for the user. Hence, we&#8217;ve introduced the concept of &#8220;notification forwarding&#8221;. This new capability allows users to define rules to forward alert notifications to another user for the specified time frames. So if you have a date tomorrow night with a supermodel and can&#8217;t be on-call, you can create a forwarding rule for the time frame you&#8217;re not available and forward your notifications to someone else, provided that and you have an understanding colleague. When you create a forwarding rule, OpsGenie would create an alert and notify both you and your colleague about the rule, and your colleague can agree to it by executing the confirm action from the alert. Alert notifications for any schedule, escalation chain, etc. during that time frame would be forwarded to your colleague instead of disturbing you during your date! Admins can create forwarding rules on behalf of users as well, to cover cases where the user is not capable of defining the exception themselves, etc. <a href="http://twitter.com/berkay">@berkay</a></p>