#### Problem to solve Now that Value Stream Analytics has been added on a group level (https://gitlab.com/gitlab-org/gitlab/issues/196455), there might be no need for the old project level page and this might therefore be removed. Otherwise, this can be confusing to clients and will require additional engineering support. HOWEVER, Based on https://about.gitlab.com/company/stewardship/ we can't simply remove the old page and not still provide the functionality to CE users. ### Intended users <!-- Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later. Personas can be found at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ --> PMs, EMs ### Further details <!-- Include use cases, benefits, and/or goals (contributes to our vision?) --> ### Proposal <!-- How are we going to solve the problem? Try to include the user journey! https://about.gitlab.com/handbook/journeys/#user-journey --> * Allow lower tier users to access group-level Value Stream Analytics, with the limitation of only being able to select a single project and not seeing any graphs * Don't allow [customizable stages](https://gitlab.com/gitlab-org/gitlab/-/issues/12196) * Remove the old project-level Value Stream Analytics * `License.feature_available?(:cycle_analytics_advanced)` would need to be passed to the FE and we should be able to display the above mentioned features based on this flag * For gitlab.com, we have the additional complication that a user can buy a namespace for himself only and can be part of both paid and unpaid groups. The current thinking is that a user can only see information under their paid namespaces/groups. * https://gitlab.slack.com/archives/C0NFPSFA8/p1562172281158100 * https://gitlab.slack.com/archives/CJZR6KPB4/p1561724760007500 ### Additional links Issue opened because of https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/30556