Skip to content

Shared group members in project cannot be selected as assignees in Issue Board sidebar anymore

Summary

After the change made by #322960 (comment 539533385), the sidebar of Issue Boards page when an issue is selected limits the search results of assignees.

However, the search is too restrictive and also omits any users that have been granted access to the project using the share-with-group features: https://docs.gitlab.com/ee/user/project/members/share_project_with_groups.html#groups-as-collections-of-users

Steps to reproduce

  1. Create two groups A, B
  2. Create a project A/Project
  3. Add some users to Group B as regular members (as Developer, or other roles)
  4. Via A/Project Members page, invite Group B (as Developer, or other role levels)
  5. Create some issues in A/Project
  6. Visit A/Project Issue Boards page
  7. Select any open issue, and try to assign it to a user belonging to Group B exclusively
  8. REGRESSION: Search does not show any members from shared Group B, only the direct and inherited group project members.

Example Project

The above was tested on 13.10.0 Self-Managed.

What is the current bug behavior?

Cannot assign issues via Issue Boards to members granted access via invited groups.

What is the expected correct behavior?

Can assign issues via Issue Boards to (at least) all project members, including those invited via another group.

Relevant logs and/or screenshots

None, functional problem affecting 13.10+ due to changes made.

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info 

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


(we will only investigate if the tests are passing)

Possible fixes