Skip to content

Update MemberApproval Table to become independent of Members

What does this MR do and why?

  1. Adds user_id, member_role_id columns
  2. Allows member_id to be nullable, this change is to account for Invited Member Approval flow which wont have a corresponding member record associated with it
  3. Updates unique index to use user_id instead of member_id, since member table almost always has user_id (unless its new user invitation flow)

ref: #433179

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Edited by Suraj Tripathi

Merge request reports