Skip to content

Ensure Cycle Analytics Project Component available for CE in the new analytics space

Problem to solve

Once the new Cycle Analytics on a group level page has been added - there will be no need for the old project level page and this can therefore be removed. Otherwise, this can be confusing to clients and will require additional engineering support.

Issue opened now already because of https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/30556

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

PMs, EMs

Further details

Proposal

  • Allow lower tier users access to the new cycle analytics page, with the limitation of only being able to select a single project and not seeing any graphs

  • Don't allow customization

  • Remove the old project level cycle analytics page

  • 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 a paid or unpaid group. 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

Edited by Virjinia Alexieva