Skip to content

Correct shared group member access level

Daphne Kua requested to merge dkua1-master-patch-aef7 into master

What does this MR do and why?

The documentation is incorrect based on the changes made on shared group member access level in MR !115346 (merged), as a result of issue #377922 (closed).

Direct members of Engineering that gain access to the Frontend group keep their same access level as in Engineering, but up to the maximum access level selected when sharing the group.

The highlighted statement is incorrect based on the following example:

  • Engineering group invited into Frontend group
  • Engineering member access level in Engineering group = Guest
  • Engineering member invited access level in Frontend = Owner
  • Actual engineering member access level in Frontend = Guest (not the maximum access level which is Owner)

How to set up and validate locally

  • Create Engineering group with Member1 as user with access level as Guest
  • Create Frontend group
  • Invite Engineering group into Frontend group as Owner

Test One Use API Get a member of a group or project for invited members to verify on the access level:

GET /groups/:id/members/all/:user_id

Access level = 10 / Guest

Test Two: Change Member1 permission in Engineering to Owner and run API, access level = 50 / Owner
Test Three: Change invited Engineering permission in Frontend to Guest and run API, access level = 10 / Guest

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Daphne Kua

Merge request reports