Projects GitLab API: response.permissions.group_access is null although user can clone the repository

Summary

Projects GitLab API: response.permissions.group_access is null although user can clone the repository.

Steps to reproduce

• I created a gitlab user - testUser.
• I created a group called group-with-developers-permissions. testUser is a member of the group with Developer role.
• I shared my project called testProject with group-with-developers-permissions (Max access level= Developer), so testUser can clone testProject repository - good
• I call gitlab rest api http:///api/v4/projects?membership=true on behalf of the testUser
• The response is:

{
    “id”: 1,
    “description”: “”,
    “default_branch”: “master”,
    …
    “permissions”:{
        “project_access”: null,
        “group_access”: null, //why group_access is null?
    }
}

Example Project

What is the current bug behavior?

“group_access”: null

What is the expected correct behavior?

“group_access”: { "access_level": 30, "notification_level": 3 },

Relevant logs and/or screenshots

Output of checks

This bug happens on GitLab EE installed on my server. { "version": "10.0.3-ee", "revision": "eff78217" }

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

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