Hey guys,

I suggest you change the default values for overrides such that the default date / time reflects the start / end times of the next scheduled shift.

https://skitch.com/ksowocki/8yxwy/pagerduty-cell-phone-on-call-schedule

kevin@stepout.com

Ability to search notes. This way I know what the previous on call person did to resolve a recurring incident. This also ends up as a valuable knowledge repository.

They support (among other) email, URL, instant messenger and SNMP trap alerting methods. We use email for sending alerts to PagerDuty, but that way PD will obviously not resolve the alert after it receives "resolved" email from websitepulse. That sucks.

There are cases where the engineer oncall is accidentally pressing "4" when he is half-awake. I suggest that we create a feature to randomize the number to ensure that the engineer is fully awake. Better yet, instead of entering one number, why not enter 3 random numbers? ie 335 for ACK 452 to RESOLVE. In this way, we are sure that the on-call is fully awake.

Would be great to have an integration with Grove.io hosted web-based IRC, where upon being paged, a user might visit their dashboard and join the hosted grove.io chat specifically for the incident.

I like to see the information very fast when I change tabs. If the page did an auto-refresh the information would show up faster.

Ability to configure method of contact used as part of an escalation policy.

Example: Create a policy that contacts person 1 by email, person 2 by SMS and person 3 by phone. This allows for raising the importance by defining a more direct method of contact as the escalation policy proceeds.

It would be great to be able to export a schedule view that includes the escalation policy and scheduling combined into one 'on call' style rota display. This could then be embedded into whatever page required.

A bit like the google calendar embedding feature.

For some schedules/services email/SMS notification is fine, and there's no reason to place a phone call. For others, I want every phone within 10 feet of me to go off. At the moment there's no way to vary this based on the severity of the event.

At the moment the only escalation rule option is "Assign the incidents to X". Could you add a "Notify X" rule, that could be inserted between assignment rules? For example, I'd like to be able to be notified when something rolls over from the first responder schedule to the backup, but don't want to be assigned the issue directly.

We have a need to have the original e-mail which triggered the incident to be forwarded to another e-mail address when the incident is resolved.

When I'm awake, notification via SMS suffices. But when I'm asleep, SMS has little chance of waking me, while a phone call has a good chance.

I currently have SMS as my first contact priority, and phone if I don't respond to that quickly. But I'd be likely to respond even faster if I could specify "only even try SMS within these hours".

we use connectwise for managing our support tickets (packettrap for system monitoring).

both have open api. it would be great to have integration

Alerts frequently come in batches. The UI makes it really hard to manage multiple related incidents. It would be nice if we could select multiple incidents and merge them / group them under a single incident. The audit trail of each individual incident would all show up on the same page.