JPI: Resource Group–Based Calendar Exceptions

The current Calendar Exceptions page does not support practical management of exceptions by Resource Group.

While the UI allows users to add Resources via a Resource Group selector, the resulting calendar exception is immediately hardcoded to the individual resources selected at that point in time. The exception does not remain dynamically linked to the Resource Group. As a result, any subsequent changes to the group—such as adding or removing resources—are not reflected in existing calendar exceptions.

This limitation creates significant administrative overhead for common use cases such as Company Holidays by Shift.  Holidays may fall on different calendar days depending on the shifts' day off and how we may opt to balance workload, so we need to define holiday exceptions at the Resource Group level, not per individual resource.

Today, if calendar exceptions are configured at the beginning of the year for a resource group:

• Newly hired employees are not automatically included in existing holiday exceptions.

• Administrators must manually locate and update every affected calendar exception to add new resources.

• The risk of missed or inconsistent holiday coverage increases over time.
  
  Holidays is just one use case that applies to everyone. Many other use cases exist for this where you'd want to manage time exceptions by resource grouping. 

Requested Enhancement

• Allow Calendar Exceptions to be defined against a Resource Group as a first-class object, not just as a one-time resource selection.

• Maintain a dynamic association so that changes to Resource Group membership automatically propagate to existing calendar exceptions.

This change would materially improve maintainability, reduce error risk, and align the Calendar Exceptions model with how Resource Groups are already used operationally for shifts and capacity planning.

________________________

Resource group Selector:

Calendar Exceptions for Company Holidays per shift: