At the moment, the system will regenerate the schedule from tomorrow if any changes are made to how the schedule would generate, i.e, if a pool is reassigned or a new person is added to the team. While this is effective, there are a few issues with it.
- Changing the data for one pool or team will regenerate the schedule for the whole organisation, even if the section that is being edited has no relation to another.
- For example, If there are two teams, Team1 and Team2 and two pools of clusters PoolA and PoolB, and Team1 was assigned PoolA and Team2 was assinged PoolB, then adding a cluster to PoolA would change the schedule for Team2, despite the changes to PoolA having no actual effect on Team2.
- If a team is changed that removes or reassigns a person that was already scheduled for today, then that person will still be scheduled for one of that team's clusters, despite not being on that team any more. The scheduler should regenerate schedules for today if they haven't completed their checks yet.
- It should account for if that person has two checks to do and they've only done one.
At the moment, the system will regenerate the schedule from tomorrow if any changes are made to how the schedule would generate, i.e, if a pool is reassigned or a new person is added to the team. While this is effective, there are a few issues with it.