Project authorizations incorrect when reassigned has existing memberships
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
It was observed that sometimes project authorizations were not correctly created after membership creation, and a fix was originally applied in !173073 (merged). However, UserProjectAccessChangedService only runs when placeholder memberships are actually reassigned. If the reassigned user is granted project memberships via inheritance, the service isn't executed, and the reassigned user is not able to view imported projects.
Import::ReassignPlaceholderUserRecordsService should be updated to run UserProjectAccessChangedService any time the source user has placeholder project memberships, not only when those project memberships have been reassigned, to ensure that project access is updated for inherited memberships.