Developer role unable to fork to ancestor group
Summary
Developer roles unable to fork to ancestor groups.
Steps to reproduce
- Create a group named
group-1
- Create and add a user to
group-1
as a developer - Create a subgroup named
group-2
ingroup-1
- Create another subgroup in
group-2
namedgroup-3
- Create a project in
group-3
namedtest-project
- Log in as the user you added to
group-1
and go totest-project
- Click to Fork
What is the current bug behavior?
After clicking fork, the user is only shown their personal namespace to fork to.
What is the expected correct behavior?
Based on our creating a fork documentation, users should be able to fork to namespaces that they are developer or higher on. However, group namespaces are only shown if they are a maintainer or higher.
Relevant logs and/or screenshots
Output of checks
This is happening on 12.9.1 to at least 12.6.4.
Results of GitLab environment info
Expand for output related to GitLab environment info
``` root@ehenley-omnibus-current:~# sudo gitlab-rake gitlab:env:info System information System: Ubuntu 18.04 Proxy: no Current User: git Using RVM: no Ruby Version: 2.6.5p114 Gem Version: 2.7.10 Bundler Version:1.17.3 Rake Version: 12.3.3 Redis Version: 5.0.7 Git Version: 2.24.1 Sidekiq Version:5.2.7 Go Version: unknown GitLab information Version: 12.9.1-ee Revision: 0ebcf602332 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: PostgreSQL DB Version: 10.12 URL: <> HTTP Clone URL: <>/some-group/some-project.git SSH Clone URL: <>:some-group/some-project.git Elasticsearch: yes Geo: no Using LDAP: no Using Omniauth: yes Omniauth Providers: GitLab Shell Version: 12.0.0 Repository storage paths: - default: /var/opt/gitlab/git-data/repositories GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell Git: /opt/gitlab/embedded/bin/git ```
Results of GitLab application Check
Expand for output related to the GitLab application check
root@ehenley-omnibus-current:~# sudo gitlab-rake gitlab:check SANITIZE=true Checking GitLab subtasks ... Checking GitLab Shell ... GitLab Shell: ... GitLab Shell version >= 12.0.0 ? ... OK (12.0.0) Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Internal API available: OK Redis available via internal API: OK gitlab-shell self-check successful Checking GitLab Shell ... Finished Checking Gitaly ... Gitaly: ... default ... OK Checking Gitaly ... Finished Checking Sidekiq ... Sidekiq: ... Running? ... yes Number of Sidekiq processes ... 1 Checking Sidekiq ... Finished Checking Incoming Email ... Incoming Email: ... Checking Reply by email ... IMAP server credentials are correct? ... yes Init.d configured correctly? ... skipped MailRoom running? ... skipped Checking Reply by email ... Finished Checking Incoming Email ... Finished Checking LDAP ... LDAP: ... LDAP is disabled in config/gitlab.yml Checking LDAP ... Finished Checking GitLab App ... Git configured correctly? ... yes Database config exists? ... yes All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory exists? ... yes Uploads directory has correct permissions? ... yes Uploads directory tmp has correct permissions? ... yes Init script exists? ... skipped (omnibus-gitlab has no init script) Init script up-to-date? ... skipped (omnibus-gitlab has no init script) Projects have namespace: ... 48/1 ... yes 48/2 ... yes 48/3 ... yes 48/4 ... yes 48/5 ... yes 48/6 ... yes 48/7 ... yes 49/8 ... yes 49/9 ... yes 49/10 ... yes 49/11 ... yes 49/12 ... yes 49/13 ... yes 49/14 ... yes 50/15 ... yes 50/16 ... yes 50/17 ... yes 51/18 ... yes 51/19 ... yes 51/20 ... yes 51/21 ... yes 51/22 ... yes 51/23 ... yes 51/24 ... yes 51/25 ... yes 51/26 ... yes 51/27 ... yes 52/28 ... yes 52/29 ... yes 52/30 ... yes 52/31 ... yes 52/32 ... yes 52/33 ... yes 52/34 ... yes 52/35 ... yes 52/36 ... yes 53/37 ... yes 53/38 ... yes 53/39 ... yes 53/40 ... yes 53/41 ... yes 53/42 ... yes 53/43 ... yes 53/44 ... yes 54/45 ... yes 54/46 ... yes 55/47 ... yes 55/48 ... yes 55/49 ... yes 55/50 ... yes 55/51 ... yes 55/52 ... yes 55/53 ... yes 56/54 ... yes 56/55 ... yes 56/56 ... yes 56/57 ... yes 56/58 ... yes 56/59 ... yes 56/60 ... yes 56/61 ... yes 56/62 ... yes 56/63 ... yes 57/64 ... yes 57/65 ... yes 57/66 ... yes 57/67 ... yes 57/68 ... yes 57/69 ... yes 58/70 ... yes 58/71 ... yes 58/72 ... yes 58/73 ... yes 58/74 ... yes 58/75 ... yes 58/76 ... yes 59/77 ... yes 59/78 ... yes 59/79 ... yes 59/80 ... yes 59/81 ... yes 59/82 ... yes 59/83 ... yes 59/84 ... yes 59/85 ... yes 59/86 ... yes 60/87 ... yes 60/88 ... yes 60/89 ... yes 60/90 ... yes 68/91 ... yes 1/92 ... yes 1/93 ... yes 1/94 ... yes 1/95 ... yes 1/96 ... yes 1/97 ... yes 78/99 ... yes 81/100 ... yes 1/101 ... yes 1/102 ... yes 1/103 ... yes 1/104 ... yes 1/105 ... yes 89/106 ... yes 68/107 ... yes 68/108 ... yes 1/109 ... yes 1/110 ... yes 1/111 ... yes 1/112 ... yes 1/113 ... yes 1/114 ... yes 68/115 ... yes 90/116 ... yes 68/117 ... yes 91/119 ... yes Redis version >= 2.8.0? ... yes Ruby version >= 2.5.3 ? ... yes (2.6.5) Git version >= 2.22.0 ? ... yes (2.24.1) Git user has default SSH configuration? ... yes Active users: ... 52 Is authorized keys file accessible? ... yes Elasticsearch version 5.6 - 6.x? ... yes (6.3.2) Checking GitLab App ... Finished Checking GitLab subtasks ... Finished
Possible fixes
Current workaround is to give the user maintainer permissions.