Allow assigning to the members of invited groups when creating assignee list on Group or project issue board
Summary
Members of invited groups are not shown in the "Select an assignee" drop-down when creating a new list in a project-level or group-level issue board.
Steps to reproduce
- Create a group called
laboratory
- Create a group called
rbac
- Create a subgroup
rbac/risk-mgmt
- Add user Alice (
@alice
) as a member of therbac/risk-mgmt
subgroup - Invite the subgroup
rbac/risk-mgmt
as a member of thelaboratory
group - Create an issue board in the
laboratory
group or in a project in thelaboratory
group - When viewing the issue boar, click Create List and select Assignee
- Click the "Select an assignee" drop down
- Observe that Alice does not appear in the list (searching for Alice yields no results)
Example Project
On GitLab.com, I created the group 213378-laboratory. I invited the subgroup 213378-rbac/risk-mgmt to be a member of 213378-laboratory
.
The undesired behavior occurs in:
What is the current bug behavior?
Members of invited groups are not shown in the "Select an assignee" drop-down when creating a new list in an issue board.
What is the expected correct behavior?
Members of invited groups should be shown in the "Select an assignee" drop-down when creating a new list in an issue board.
Relevant logs and/or screenshots
Output of checks
This bug happens on GitLab.com and on a self-managed instance running 13.11.3.
Results of GitLab environment info
Expand for output related to GitLab environment info
System information System: Ubuntu 18.04 Proxy: no Current User: git Using RVM: no Ruby Version: 2.7.2p137 Gem Version: 3.1.4 Bundler Version:2.1.4 Rake Version: 13.0.3 Redis Version: 6.0.12 Git Version: 2.31.1 Sidekiq Version:5.2.9 Go Version: unknown GitLab information Version: 13.11.3-ee Revision: 7fde0affe23 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: PostgreSQL DB Version: 12.6 URL: https://omg.brie.dev HTTP Clone URL: https://omg.brie.dev/some-group/some-project.git SSH Clone URL: git@omg.brie.dev:some-group/some-project.git Elasticsearch: no Geo: no Using LDAP: yes Using Omniauth: yes Omniauth Providers: auth0 GitLab Shell Version: 13.17.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
Checking GitLab subtasks ...
Checking GitLab Shell ...
GitLab Shell: ... GitLab Shell version >= 13.17.0 ? ... OK (13.17.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 (cluster/worker) ... 1/1
Checking Sidekiq ... Finished
Checking Incoming Email ...
Incoming Email: ... Checking Reply by email ...
IMAP server credentials are correct? ... Checking bot@briecarranza.com yes Init.d configured correctly? ... skipped MailRoom running? ... skipped
Checking Reply by email ... Finished
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 8 users of 100 limit.
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: ... 2/1 ... yes 4/2 ... yes 4/3 ... yes 5/4 ... yes 5/5 ... yes 6/6 ... yes 6/7 ... yes 1/8 ... yes 9/9 ... yes 5/10 ... yes 1/11 ... yes 5/12 ... yes 1/13 ... yes 13/14 ... yes 19/15 ... yes 20/16 ... yes 20/17 ... yes 20/18 ... yes 19/19 ... yes 5/25 ... yes 1/26 ... yes 25/27 ... yes 26/28 ... yes 28/29 ... yes 28/30 ... yes 28/31 ... yes 33/32 ... yes 35/33 ... yes 31/34 ... yes Redis version >= 5.0.0? ... yes Ruby version >= 2.7.2 ? ... yes (2.7.2) Git version >= 2.31.0 ? ... yes (2.31.1) Git user has default SSH configuration? ... yes Active users: ... 9 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 (6.4 - 6.x deprecated to be removed in 13.8)? ... skipped (elasticsearch is disabled)
Checking GitLab App ... Finished
Checking GitLab subtasks ... Finished
(we will only investigate if the tests are passing)
Possible fixes
📓 Notes
When I create an issue in a project in laboratory
, I can see the members of the invited rbac/risk-mgmt
group in the assignee list. (I believe that this is expected.) I can't see them when creating an Assignee list in an issue board.
This is similar to the Allow assigning to the members of descendant groups when creating assignee list on Group issue board issue. That issue is a spin-off from Some project members are not included in the new assignees dropdown.