Clarify group assignment using quick actions
Summary
Although 'assignment of group members in quick actions' has been implemented in !90843 (merged), the behaviour of passing a group has not been documented: https://docs.gitlab.com/ee/user/project/quick_actions.html (only users are mentioned).
Steps to reproduce
See 'Summary'.
Example Project
What is the current bug behavior?
When using /assign followed by a group in issues, I would expect all members in that group to become assignees.
When using /assign followed by a group in PRs, I would expect a random user in that group to become the assignee (as PRs don't support multiple assignees).
When using /assign_reviewer followed by a group in PRs, I would expect all members in that group to become reviewers.
What is the expected correct behavior?
I'm not sure what behaviour I am seeing. I am a member of all groups. When I perform any of the actions above, the resource is assigned to me and only me. The same happens when another user does this (I am assigned). I'm not sure why I would be a special case (first in the group, maybe?).
Relevant logs and/or screenshots
Output of checks
On self-hosted EE.
Results of GitLab environment info
Expand for output related to GitLab environment info
root@gitlab0:~# gitlab-rake gitlab:env:info System information System: Debian 12 Proxy: no Current User: git Using RVM: no Ruby Version: 3.2.5 Gem Version: 3.5.23 Bundler Version:2.5.11 Rake Version: 13.0.6 Redis Version: 7.0.15 Sidekiq Version:7.2.4 Go Version: unknown GitLab information Version: 17.8.1-ee Revision: a303ad659b5 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: PostgreSQL DB Version: 14.15 URL: https://vcs.cyberfusion.nl HTTP Clone URL: https://vcs.cyberfusion.nl/some-group/some-project.git SSH Clone URL: git@vcs.cyberfusion.nl:some-group/some-project.git Elasticsearch: no Geo: no Using LDAP: yes Using Omniauth: yes Omniauth Providers: GitLab Shell Version: 14.39.0 Repository storages: - default: unix:/var/opt/gitlab/gitaly/gitaly.socket GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell Gitaly - default Address: unix:/var/opt/gitlab/gitaly/gitaly.socket - default Version: 17.8.1 - default Git Version: 2.47.0
Results of GitLab application Check
Expand for output related to the GitLab application check
root@gitlab0:~# gitlab-rake gitlab:check SANITIZE=true Checking GitLab subtasks ...
Checking GitLab Shell ...
GitLab Shell: ... GitLab Shell version >= 14.39.0 ? ... OK (14.39.0) Running /opt/gitlab/embedded/service/gitlab-shell/bin/gitlab-shell-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 (cluster/worker) ... 1/1
Checking Sidekiq ... Finished
Checking Incoming Email ...
Incoming Email: ... Reply by email is disabled in config/gitlab.yml
Checking Incoming Email ... Finished
Checking LDAP ...
LDAP: ... Server: ldapmain LDAP authentication... Success LDAP users with access to your GitLab server (only showing the first 100 results) User output sanitized. Found 24 users of 100 limit.
Checking LDAP ... Finished
Checking GitLab App ...
Database config exists? ... yes Tables are truncated? ... skipped All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Cable config exists? ... yes Resque config exists? ... 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 Systemd unit files or init script exist? ... skipped (omnibus-gitlab has neither init script nor systemd units) Systemd unit files or init script up-to-date? ... skipped (omnibus-gitlab has neither init script nor systemd units) Projects have namespace: ... 183/24 ... yes 39/28 ... yes 39/40 ... yes 183/41 ... yes 182/48 ... yes 2/57 ... yes 183/63 ... yes 2/67 ... yes 183/80 ... yes 39/83 ... yes 183/87 ... yes 183/89 ... yes 183/91 ... yes 38/93 ... yes 183/95 ... yes 39/101 ... yes 183/103 ... yes 183/106 ... yes 183/107 ... yes 182/109 ... yes 22/114 ... yes 183/116 ... yes 44/117 ... yes 183/121 ... yes 183/122 ... yes 183/123 ... yes 38/124 ... yes 183/125 ... yes 183/126 ... yes 183/127 ... yes 183/128 ... yes 183/129 ... yes 183/131 ... yes 183/132 ... yes 183/133 ... yes 38/135 ... yes 183/136 ... yes 39/137 ... yes 39/138 ... yes 39/139 ... yes 183/140 ... yes 183/142 ... yes 183/143 ... yes 183/144 ... yes 183/145 ... yes 183/146 ... yes 183/147 ... yes 183/148 ... yes 183/149 ... yes 39/150 ... yes 183/151 ... yes 183/152 ... yes 39/153 ... yes 302/154 ... yes 223/156 ... yes 223/157 ... yes 38/158 ... yes 183/159 ... yes 183/160 ... yes 183/161 ... yes 183/162 ... yes 183/164 ... yes 301/171 ... yes 301/172 ... yes 183/173 ... yes 183/174 ... yes 301/175 ... yes 183/176 ... yes 183/177 ... yes 182/180 ... yes 183/181 ... yes 272/182 ... yes 183/183 ... yes 183/184 ... yes 183/185 ... yes 183/186 ... yes Redis version >= 6.2.14? ... yes Ruby version >= 3.0.6 ? ... yes (3.2.5) Git user has default SSH configuration? ... yes Active users: ... 15 Is authorized keys file accessible? ... yes GitLab configured to store new projects in hashed storage? ... yes All projects are in hashed storage? ... yes Elasticsearch version 7.x-8.x or OpenSearch version 1.x ... skipped (Advanced Search is disabled) All migrations must be finished before doing a major upgrade ... skipped (Advanced Search is disabled)
Checking GitLab App ... Finished
Checking GitLab subtasks ... Finished