Can PagerDuty please post an update on this request? There are at least two other closely related request.
All three of these requests are years old. The PT Product team promised some improvements in March of 21. The promise was too vague to know if they ever came out but the fact remains that the current worflow is schedule-centric, vs. user-centric. This is a significant failure to understand how your users use the system.
I have my second senior SRE going on month-long paternity leave this year. Each of these people are on multiple on-call schedules. As with most of the schedules that people have describe around this problem, they are only on call for a period day each day. This leaves me, or them, with literally hundreds of overrides to make. Each requires three clicks, typing in at least part of the name of the person taking the shift, and two waiting periods, one for a dropdown of users to populate, and a second for the override to save. I work for a SaaS company. This kind of workflow in a key use case, simply isn’t acceptable.
For my use case (and I think most of the ones described) the solution would entail starting with the user going on leave, and the period of time for which they will be on leave and show all rotations they will be on duty for in that timeframe. Then for each rotation, select start and end date (default to the original timeframe selected), and an alternative staff member, and assign them as overrides to all in-scope shifts. Rinse and repeat until all shifts on all rotations are covered.
I would be happy to discuss this further if PD should have questions. In the mean time though, please excuse, as I have a lot of clicking to do…