Value streams dashboard not fully visible when user is not a member of project's parent group

Summary

The Value Streams Analytics dashboard is not fully visible when said user has Reporter or greater role in the project itself, but are not a member of the project's parent group. This results in DORA and Security metrics being missing from the dashboard with an error stating it requires an Ultimate plan.

image

This feature requires an Ultimate plan Learn more.

This project is in an Ultimate namespace.

Alongside a pop up stating:

You have insufficient permissions to view: Lead time, Cycle time, Issues created, Issues closed, Deploys, Median time to merge

When the same user is added as a member of the parent group that contains the project, they are able to see the dashboard as expected.

image

Steps to reproduce

  1. Create a subgroup and project within an Ultimate namespace
  2. Add a test user to the project itself as Reporter or above
  3. As the test user, navigate to the Analytics dashboards, then select Value Streams Dashboard
  4. Observe the error
  5. Add the test user to the parent subgroup that contains the project, a role of Reporter or above.
  6. As the test user, refresh the Value Streams Dashboard.
  7. Observe the DORA and Security metrics appear

Example Project

N/A

What is the current bug behaviour?

Users who are not members of a project's parent group are unable to see all metrics in the Value Streams Dashboard. Even though they have sufficient permissions in the project itself.

What is the expected correct behaviour?

Users should be able to view the Value Streams Dashboard regardless of parent group membership, provided they have sufficient permissions in the project itself.

Relevant logs and/or screenshots

image

image

Output of checks

This bug happens on GitLab.com

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

Patch release information for backports

If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.

Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.

High-severity bug remediation

To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.

Edited by 🤖 GitLab Bot 🤖