Forking does not inherit project component visibility settings

Summary

We have a project which is public, but limits access to the repo/wiki/snippets to 'Only Project Members'. We have this setup to expose the issue tracker publicly, but keep the code within our repo hidden from the world.

Whenever we fork the project, the fork inherits the top-level visibility (e.g. public), but does not inherit the permissions settings for the project components. In the user's fork, the repo/wiki/snippets are fully public, that is visibility is set to 'Everyone With Access'.

Steps to reproduce

  1. have a project (ID: 1) that is public, with repository visibility set to 'Only Project Members'
  2. fork project 1, which inherits the public permission.
  3. the permissions tree in Settings shows that repository visibility is set to 'Everyone with Access'

Example Project

I've created group hv15-test-group with project TESTPROJECT (https://gitlab.com/hv15-test-group/testproject), I have forked this to my namespace https://gitlab.com/hv15/testproject. The fork inherits the top-level permission, but not the component visibility settings.

What is the current bug behavior?

Only the top-level project visibility setting is inherited when forking.

What is the expected correct behavior?

All visibility permissions should be inherited when forking, for each component of the project.

Relevant logs and/or screenshots

Main Project

orig

Fork

fork

Output of checks

This bug happens on GitLab.com