Skip to content

Group project template cannot be seen by inherited member

Summary

When users try to create a project from a custom group level project template, the project template is not visible to inherited member. Even when the project is set to Public and allow access to Everyone with access, it is still invisible.

Steps to reproduce

  1. Setup the custom group-level project template in subgroup A under the top level group
  2. Add members to the top level group with Reporter permission
  3. Create a new subgroup B under the top level group for new projects
  4. Escalate permission for members in subgroup B to Developer/Maintainer
  5. Try to create a new project in subgroup B from the custom project template and see that the group template is not showing up

Other variation:

  1. Escalate the member permission to Maintainer in subgroup B and add subgroup B as a member with Maintainer permission in the subgroup A also doesn't work
  2. Set subgroup A and the projects under subgroup A to Public and set all the project permission to Everyone with access as mentioned in the doc also doesn't work

Example Project

What is the current bug behavior?

Inherited members cannot see the group project template unless added directly to the project template group one by one.

What is the expected correct behavior?

Member who has access should be able to create a new project using the templates.

Relevant logs and/or screenshots

Output of checks

This bug happens on GitLab.com; GitLab Enterprise Edition 13.8.0-pre 7fe9a596efe

Results of GitLab environment info

Expand for output related to GitLab environment info 

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


(we will only investigate if the tests are passing)

Possible fixes

Customers

customer contact
https://gitlab.zendesk.com/agent/tickets/184830 @rotanak
https://gitlab.my.salesforce.com/0016100001bNIWb @ricardoamarilla
https://gitlab.zendesk.com/agent/tickets/254818  @vidhya.h
https://gitlab.my.salesforce.com/00161000015MAsEAAW @manuel.kraft , @lwbrown

Current status

Update on 2024-04-10 from slack convo and comment.

Self-managed:

The fix is currently under the :project_templates_without_min_access feature flag: [Feature flag] Rollout of `project_templates_wi... (#425452 - closed). Self-managed customers can enable the feature flag to resolve the issue.

GitLab.com:

Performance issues are blocking the feature flag rollout on gitlab.com. Solutions are being investigated and discussed in Investigate other solutions to the performance ... (#441462 - closed). Once the performance issues have been addressed, it is expected that the feature flag can be enabled on gitlab.com.

Edited by Donique Smit