Group permissions don't apply to created projects
Summary
A user who is a master in a group, upon creating a project in that group, does not have elevated access to the project.
An admin needs to add the user to the project itself and then they would have access, which makes me think it's a bug
Steps to reproduce
- Create a group and assign a non-admin user as master
- Have that user create a project in the group
- The user doesn't have any admin rights to the project, but they should. Only "Members" is visible in the gear.
- As an administrator, manually add the user to the project and make them a master
- User now has access.
What is the current bug behavior?
It seems like group permissions are not carrying over to the project.
What is the expected correct behavior?
Group permissions should be applied to the projects.
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
GitLab 8.16.5-ee
GitLab Shell 4.1.1
GitLab Workhorse v1.3.0
GitLab API v3
Git 2.11.0
Ruby 2.3.0p0
Rails 4.2.7.1
Mysql2 5.5.54-0+deb7u1
Possible fixes
This seems like https://gitlab.com/gitlab-org/gitlab-ce/issues/27558 but that is for the project creator not getting owner privileges. In this case the project creator gets only the ability to list members and nothing else.
Maybe also https://gitlab.com/gitlab-org/gitlab-ce/issues/26369
This issue may be a duplicate of https://gitlab.com/gitlab-org/gitlab-ce/issues/26194
In the above issue it was marked as a 9.0 fix, but this is a really annoying bug and hopefully it can be fixed in 8.x at least for EE customers who depend on it.