I don't know if the following behaviour is by design, but it is causing us some grief.

We have defined a Group/Sub-group hierarchy, where the Group Name reflects the course that a student is enrolled upon, and where there are multiple groups (because of student numbers, or multiple years) we define one or more subgroups. So for example, we define a Group 'APHE01' and within that subgroup 'APHE01A1'  - Group A, Year 1; and subgroup 'APHE01B1' - Group B, Year 1.

We have found that if staff create an event at the Group 'APHE01' level, then the event is propagated down to all subgroups. That in itself, is probably quite useful. However, if the subgroup APHE01A1 should NOT actually be timetabled for that event and that event is deleted from the 'APHE01A1' timetable, then the event is ALSO DELETED at the Group level AND from ALL other sub-groups contained within that Group!! 

Has anyone else come across this behaviour?

Hi Keith

We also use groups and subgroups. In the scenario you describe, if the event was only applicable to some of the subgroups, then we'd create the event at subgroup level rather than at the top level. E.g. create the event for APHE01B1 and APHE01C1 but not for APHE01A1. It then filters down to student members of those groups but not up to APHE01 or sideways to APHE01A1.

Best wishes

Jenny