Fix feature flag for cycle analytics / productivity analytics
Summary
(Summarize the bug encountered concisely)
We should have a feature flag for each feature we are releasing:
Productivity analytics should be enabled by 'analytics' and 'productivity analytics'. Currently, enabling 'analytics', enables 'productivity analytics' and 'cycle analytics'. Because of that we cannot currently enable cycle analytics. This should be fixed so that the 2 features are independent and since we refer to this in the docs. This is fixed in the productivity analytics MR, but it has been in review for 4 weeks, so we need to ship the fix faster.
Let's have an independent flag for 'productivity analytics' and another one for 'cycle analytics' on top of the 'analytics' workspace.
https://docs.gitlab.com/ee/user/analytics/index.html
https://gitlab.slack.com/archives/CBFCUM0RX/p1566207498239500
Steps to reproduce
(How one can reproduce the issue - this is very important)
Example Project
(If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report)
(If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version)
What is the current bug behavior?
(What actually happens)
What is the expected correct behavior?
(What you should see instead)
Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.)
Output of checks
(If you are reporting a bug on GitLab.com, write: 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
(If you can, link to the line of code that might be responsible for the problem)