Start by building out just shift recurrence (without assigning volunteers) using PMM Service Schedules as a model. We'll add Shift Assignments as a separate issue.
Information about the schedule itself should be persisted as a custom object called Volunteer Shift Schedule. This is intentionally specific. While we may choose to organize the more generic recurrence classes into a recurrence subfolder, there is no desire to make a generic recurrence engine like we discussed with emails.
Volunteer Shift Schedule should include the following fields based on Service Schedule in PMM:
Create Volunteer Shift Records (boolean)
Days of Week (multiselect picklist)
First Shift End (date/time)
First Shift Start (date/time)
Frequency
Interval
Maximum Volunteers Allowed
Minimum Volunteers Required
Monthly Recurrence Option
Number of Shifts
Shift Schedule End Date
Shift Schedule Ends
Volunteer Activity (lookup)
To limit the scope of the initial work, you may choose to leave out adding or removing shifts from this UI. That's fine as long as you create a follow-up issue to address that work.
Start by building out just shift recurrence (without assigning volunteers) using PMM Service Schedules as a model. We'll add Shift Assignments as a separate issue.
Information about the schedule itself should be persisted as a custom object called Volunteer Shift Schedule. This is intentionally specific. While we may choose to organize the more generic recurrence classes into a recurrence subfolder, there is no desire to make a generic recurrence engine like we discussed with emails.
Volunteer Shift Schedule should include the following fields based on Service Schedule in PMM:
To limit the scope of the initial work, you may choose to leave out adding or removing shifts from this UI. That's fine as long as you create a follow-up issue to address that work.