I've come across a conflict between schedules used to represent the working hours of general users and on-call schedules. As an organization, we are using PPM and Service Operations Workspace.
For PPM, we have a default/generic schedule used to represent the working hours of regular users, with child schedules representing holidays. This is the recommended practice in PPM to calculate resource capacity correctly.
There are 2 issues we are seeing:
1. When on-call users are provided as coverage, their schedule entry get's added to the PM Schedule. Then, when users update tasks or projects the end date/time and duration calculations are getting messed up.
2. When attempting to 'provide coverage' in Service Operations Workspace. We have a number of users in an on-call group. When I attempt to provide coverage with a user in that group that has the default schedule, then all users within the group that have the default schedule are displayed in the On-Call Service Operations Workspace. However, within the Default Schedule, there is only a single Roster Schedule Entry that gets added for the shift coverage that is only for the user that was selected (not for all the users visually displayed in workspace). See screengrab where i 'provided coverage' for Name 3 with Name 1, and Name 1, 2, & 3 all have default schedule.
How can the on-call users also be allocated to projects with accurate availability if they don't have a schedule? Is there a different way to create a schedule for these users?
