Cycle Analytics - CE vs EE, permissions

Problem to solve

Currently we have a baseline cycle analytics page, which is community edition. https://gitlab.com/gitlab-org/gitlab-ce/cycle_analytics. Given we are developing cycle analytics on a group and instance level and want to combine all analytics under the analytics tab, we should figure out a way to allow CE users to only see this chart from our new Cycle Analytics Page.

Intended users

PMs, EMs

Further details

Proposal

1. On the filtering side we can disable any other filters but 1 project
2. Can we hide all the additional graphs on the page for CE?
3. 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. @valexieva to figure out a solution on this but the current thinking is that a user can only see information under their paid namespaces.

• https://gitlab.slack.com/archives/C0NFPSFA8/p1562172281158100
• https://gitlab.slack.com/archives/CJZR6KPB4/p1561724760007500
• needs thinking about projects under individual spaces and subgroups

Permissions and Security

Documentation

Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Links / references