When creating a Resource Assignment where Assignment type is Group, whether a Task or Operational RA, the RA remains assigned to the Users in the Group at the point of the creation of the RA. When people are added to a Group, they do not get added to existing Group RAs, or when people are removed from a Group, they remain behind for existing Group RAs which steals the availability for their new team for work that may not have followed them to their new team.
What are we supposed to do for these situations? Our agile teams like using Group RAs so that they can track the team's capacity/availability while maintaining the flexibility to shift specific resources across projects from sprint to sprint without the overhead of moving User RAs around all of the time.
One idea I had: add the Split action to the Parent RA for these Group assignments, and when it does the split, it could use the current group membership.
