Skip to content

BE: Add logic to queue valid Members for Promotion Approval

Current Member Update behaviour, when an Existing Project/Group Member <= Guest user is promoted to a higher role:

1. A Put Request goes to "groups/<group_name>/-/group_members/record_id", i.e MembershipActions#update method
2. The flow moves here and triggers "Members::UpdateService" with the valid parameters
3. Users "Role" updates and other cascading changes take place as part of the UpdateService

Expected:

If !141515 (diffs) returns true, instead of triggering the MembershipAction, queue the request in the table and return meaning full message to FE

Edited by Suraj Tripathi