Projects cannot be transferred to subgroup created by others unless permission is explicitly granted

Summary

When trying so transfer a project from a group to a subgroup the subgroup cannot be selected in the dropdown menu. When viewing the member list of the subgroup I'm inheriting the "Owner" permission from the main group. When I explicitly add myself as Owner to the subgroup (which seems to support the fact that my permissions are inherited) I can transfer the project.

We're using LDAP for user access, maybe this is a problem? I have no instance with local user accounts available.

Steps to reproduce

1. Create a group
2. Be Owner in this group
3. Assign Owner permissions to another user
4. Let another user create a subgroup within the main group
5. Try to transfer a project to this subgroup

What is the current bug behavior?

The dropdown when transferring a subproject doesn't show the subgroup created by another user.

What is the expected correct behavior?

The dropdown when transferring a subproject should show the subgroup created by another user.

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

System information System: Ubuntu 14.04 Current User: git Using RVM: no Ruby Version: 2.3.3p222 Gem Version: 2.6.6 Bundler Version:1.13.7 Rake Version: 10.5.0 Redis Version: 3.2.5 Git Version: 2.11.1 Sidekiq Version:4.2.7

GitLab information
Version:    9.1.0
Revision:    c3f0f14
Directory:    /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:    postgresql
URL:        https://gitlab.rz.krzn.de
HTTP Clone URL:    https://gitlab.rz.krzn.de/some-group/some-project.git
SSH Clone URL:    git@gitlab.rz.krzn.de:some-group/some-project.git
Using LDAP:    yes
Using Omniauth:    no

GitLab Shell
Version:    5.0.2
Repository storage paths:
- default:     /srv/gitlab/repos/repositories
Hooks:        /opt/gitlab/embedded/service/gitlab-shell/hooks
Git:        /opt/gitlab/embedded/bin/git

Results of GitLab application Check

Checking GitLab Shell ...

GitLab Shell version >= 5.0.2 ? ... OK (5.0.2)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by git:git?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ...
120/3 ... ok
120/4 ... ok
7/5 ... ok
5/6 ... ok
5/7 ... ok
5/8 ... ok
120/9 ... ok
5/10 ... repository is empty
11/13 ... ok
5/14 ... ok
19/15 ... ok
19/20 ... ok
19/24 ... ok
14/25 ... ok
14/26 ... ok
100/27 ... ok
17/32 ... ok
17/33 ... ok
10/36 ... ok
17/37 ... ok
7/38 ... ok
5/39 ... ok
27/41 ... ok
27/42 ... ok
28/43 ... ok
28/44 ... ok
32/46 ... ok
17/47 ... repository is empty
17/48 ... ok
68/49 ... ok
68/50 ... ok
68/51 ... ok
5/53 ... ok
5/55 ... ok
27/56 ... ok
77/57 ... ok
19/58 ... ok
77/59 ... ok
77/60 ... ok
19/62 ... ok
5/66 ... ok
5/67 ... ok
5/68 ... ok
5/69 ... ok
5/70 ... ok
5/71 ... ok
19/73 ... ok
19/74 ... ok
85/78 ... ok
14/80 ... repository is empty
10/81 ... repository is empty
14/82 ... ok
5/83 ... ok
27/86 ... ok
25/88 ... ok
21/90 ... repository is empty
4/91 ... repository is empty
16/92 ... repository is empty
4/94 ... repository is empty
12/95 ... ok
86/96 ... ok
3/97 ... repository is empty
21/98 ... repository is empty
11/99 ... repository is empty
3/100 ... repository is empty
12/101 ... repository is empty
4/102 ... ok
59/104 ... ok
62/105 ... ok
86/107 ... ok
86/108 ... ok
86/109 ... ok
86/110 ... ok
86/111 ... ok
86/112 ... ok
86/114 ... ok
122/115 ... ok
5/116 ... ok
86/117 ... ok
86/118 ... repository is empty
17/119 ... ok
10/120 ... ok
11/121 ... ok
11/123 ... ok
35/124 ... repository is empty
11/125 ... ok
19/126 ... ok
120/127 ... ok
76/129 ... repository is empty
76/134 ... ok
53/136 ... ok
77/139 ... ok
5/141 ... ok
10/142 ... ok
5/148 ... ok
92/149 ... ok
95/150 ... ok
92/156 ... ok
92/157 ... ok
92/158 ... ok
92/159 ... ok
92/160 ... ok
96/162 ... ok
96/163 ... ok
5/166 ... ok
5/167 ... ok
5/168 ... ok
10/169 ... ok
92/171 ... ok
92/174 ... ok
5/175 ... ok
10/176 ... repository is empty
92/177 ... ok
60/178 ... ok
122/179 ... ok
5/181 ... ok
99/182 ... ok
122/183 ... ok
5/184 ... ok
89/185 ... ok
100/187 ... ok
100/188 ... ok
89/189 ... ok
101/190 ... ok
122/191 ... ok
95/192 ... ok
100/194 ... ok
122/195 ... ok
107/196 ... ok
7/197 ... ok
39/199 ... ok
7/200 ... ok
19/201 ... ok
5/202 ... ok
110/203 ... ok
110/204 ... ok
110/205 ... ok
110/206 ... ok
92/207 ... ok
27/210 ... ok
100/211 ... ok
91/212 ... ok
83/213 ... repository is empty
84/215 ... repository is empty
100/216 ... ok
110/217 ... ok
94/218 ... ok
94/219 ... ok
94/220 ... ok
118/221 ... ok
94/222 ... ok
5/223 ... ok
95/224 ... ok
119/225 ... ok
122/226 ... ok
62/227 ... ok
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Access to /var/opt/gitlab/.ssh/authorized_keys: OK
Send ping to redis server: OK
gitlab-shell self-check successful

Checking GitLab Shell ... Finished

Checking Sidekiq ...

Running? ... yes
Number of Sidekiq processes ... 1

Checking Sidekiq ... Finished

Checking Reply by email ...

Reply by email is disabled in config/gitlab.yml

Checking Reply by email ... Finished

Checking LDAP ...

Server: ldapmain
LDAP authentication... Success
LDAP users with access to your GitLab server (only showing the first 100 results)

Checking LDAP ... Finished

Checking GitLab ...

Git configured with autocrlf=input? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config outdated? ... no
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory setup correctly? ... 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: ...
120/3 ... yes
120/4 ... yes
7/5 ... yes
5/6 ... yes
5/7 ... yes
5/8 ... yes
120/9 ... yes
5/10 ... yes
11/13 ... yes
5/14 ... yes
19/15 ... yes
19/20 ... yes
19/24 ... yes
14/25 ... yes
14/26 ... yes
100/27 ... yes
17/32 ... yes
17/33 ... yes
10/36 ... yes
17/37 ... yes
7/38 ... yes
5/39 ... yes
27/41 ... yes
27/42 ... yes
28/43 ... yes
28/44 ... yes
32/46 ... yes
17/47 ... yes
17/48 ... yes
68/49 ... yes
68/50 ... yes
68/51 ... yes
5/53 ... yes
5/55 ... yes
27/56 ... yes
77/57 ... yes
19/58 ... yes
77/59 ... yes
77/60 ... yes
19/62 ... yes
5/66 ... yes
5/67 ... yes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 5/68 ... yes
5/69 ... yes
5/70 ... yes
5/71 ... yes
19/73 ... yes
19/74 ... yes
85/78 ... yes
14/80 ... yes
10/81 ... yes
14/82 ... yes
5/83 ... yes
27/86 ... yes
25/88 ... yes
21/90 ... yes
4/91 ... yes
16/92 ... yes
4/94 ... yes
12/95 ... yes
86/96 ... yes
3/97 ... yes
21/98 ... yes
11/99 ... yes
3/100 ... yes
12/101 ... yes
4/102 ... yes
59/104 ... yes
62/105 ... yes
86/107 ... yes
86/108 ... yes
86/109 ... yes
86/110 ... yes
86/111 ... yes
86/112 ... yes
86/114 ... yes
122/115 ... yes
5/116 ... yes
86/117 ... yes
86/118 ... yes
17/119 ... yes
10/120 ... yes
11/121 ... yes
11/123 ... yes
35/124 ... yes
11/125 ... yes
19/126 ... yes
120/127 ... yes
76/129 ... yes
76/134 ... yes
53/136 ... yes
77/139 ... yes
5/141 ... yes
10/142 ... yes
5/148 ... yes
92/149 ... yes
95/150 ... yes
92/156 ... yes
92/157 ... yes
92/158 ... yes
92/159 ... yes
92/160 ... yes
96/162 ... yes
96/163 ... yes
5/166 ... yes
5/167 ... yes
5/168 ... yes
10/169 ... yes
92/171 ... yes
92/174 ... yes
5/175 ... yes
10/176 ... yes
92/177 ... yes
60/178 ... yes
122/179 ... yes
5/181 ... yes
99/182 ... yes
122/183 ... yes
5/184 ... yes
89/185 ... yes
100/187 ... yes
100/188 ... yes
89/189 ... yes
101/190 ... yes
122/191 ... yes
95/192 ... yes
100/194 ... yes
122/195 ... yes
107/196 ... yes
7/197 ... yes
39/199 ... yes
7/200 ... yes
19/201 ... yes
5/202 ... yes
110/203 ... yes
110/204 ... yes
110/205 ... yes
110/206 ... yes
92/207 ... yes
27/210 ... yes
100/211 ... yes
91/212 ... yes
83/213 ... yes
84/215 ... yes
100/216 ... yes
110/217 ... yes
94/218 ... yes
94/219 ... yes
94/220 ... yes
118/221 ... yes
94/222 ... yes
5/223 ... yes
95/224 ... yes
119/225 ... yes
122/226 ... yes
62/227 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.1.0 ? ... yes (2.3.3)
Your git bin path is "/opt/gitlab/embedded/bin/git"
Git version >= 2.7.3 ? ... yes (2.11.1)
Active users: 44

Checking GitLab ... Finished

Possible fixes

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

This also seems to be the case when creating a new project, as both "actions" seem to share the same dropdown.

mentioned in issue #31724 (closed)

mentioned in issue #31725 (moved)

The same experience in GitLab 9.1.2

I was hoping that issue #30194 (closed) will fix this, but it didn't.

Would be great if it will work the way @linus9000 described above.

added Platform subgroups labels

moved to gitlab#9467

Hey!

GitLab is moving all development for both GitLab Community Edition and Enterprise Edition into a single codebase. The current gitlab-ce repository will become a read-only mirror, without any proprietary code. All development is moved to the current gitlab-ee repository, which we will rename to just gitlab in the coming weeks. As part of this migration, issues will be moved to the current gitlab-ee project.

If you have any questions about all of this, please ask them in our dedicated FAQ issue.

https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

You can also find more information here:

• https://gitlab.com/gitlab-org/gitlab-ee/issues/13304
• https://about.gitlab.com/2019/08/23/a-single-codebase-for-gitlab-community-and-enterprise-edition/

Frequently Asked Questions

For an up to date list of questions and answers, please take a look at https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

What will we do with the repository names?

https://gitlab.com/gitlab-org/gitlab-ee/ will become https://gitlab.com/gitlab-org/gitlab, and https://gitlab.com/gitlab-org/gitlab-ce will become https://gitlab.com/gitlab-org/gitlab-foss.

Why rename gitlab-ce to gitlab-foss?

Using "gitlab" and "gitlab-ce" would be confusing, so we decided to rename gitlab-ce to gitlab-foss to make the purpose of this FOSS repository more clear

I created a merge requests for CE, and this got closed. What do I need to do?

You will need to create a merge request at https://gitlab.com/gitlab-org/gitlab-ee/. This link will eventually redirect to https://gitlab.com/gitlab-org/gitlab.

How does the licensing work in this new setup?

Everything in the ee/ directory is proprietary. Everything else is free and open source software. If your merge request does not change anything in the ee/ directory, the process of contributing changes is the same as when using the gitlab-ce repository.

Will you accept merge requests on the gitlab-ce/gitlab-foss project after it has been renamed?

No. Merge requests submitted to this project will be closed automatically.

Will I still be able to view old issues and merge requests in gitlab-ce/gitlab-foss?

Yes.

How will this affect users of GitLab CE using Omnibus?

No changes will be necessary, as the packages built remain the same.

How will this affect users of GitLab CE that build from source?

Once the project has been renamed, you will need to change your Git remotes to use this new URL. GitLab will take care of redirecting Git operations so there is no hard deadline, but we recommend doing this as soon as the projects have been renamed.

Where can I see a timeline of the remaining steps?

https://gitlab.com/gitlab-org/gitlab-ee/issues/13304

Will community contributions submitted to the new "gitlab" repository be available in the new gitlab-foss repository?

Yes, these changes will be synced to gitlab-foss automatically, several times per day.

locked this issue

mentioned in issue gitlab#9598