Skip to content

Unblocked users cannot see group projects added while they are blocked

Summary

Users that are blocked then subsequently unblocked are unable to see group projected added when they were blocked.

It is possible to workaround this issue by changing the permissions level of the user in the group.

Reported (Zendesk, internal use) by a 360-seat starter customer.

Steps to reproduce

  • Create a group, "group1"
  • Permissions are assigned at group level
  • Ensure a user "user1" has maintainer permission on the group (and is not an admin user)
  • Block the user "user1"
  • Create a new project within the group "group1". Call this "project2". No users are explicitly added to the project, they're all inherited from the group.
  • Unblock the user "user1"
  • Sign in to GitLab as "user1"
  • Go to the "group1" group page. Observe that "project2" is missing.
  • Try to enter the project2 URL directly. Get a 404 error.
  • Observe that if another user looks at the Members page on "project2", then "user1" is correctly listed as a Maintainer, so the Members list is inconsistent with the actual permissions that GitLab is using.

Example Project

N/A

What is the current bug behavior?

When the user is unblocked, they are not able to see group projects added while they were blocked

What is the expected correct behavior?

When the user is unblocked, they should be able to see all group projects

Relevant logs and/or screenshots

N/A

Output of checks

Customer reported this happens on 11.11.5-ee.

I managed to reproduce this on 12.0.3-ee.

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)