Separate repository analytics and group coverage licensing
What does this MR do?
This merge request is a proposed follow-up to #259611 (closed). We've removed the group_coverage_reports
feature flag, so the checks left in the controllers here are redundant or unecessary. I've updated the specs as well to ensure the behavior stays consistent across CoverageReports
and RepositoryAnalytics
Screenshots
Does this MR meet the acceptance criteria?
Conformity
Changelog entry-
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides Database guides-
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. Tested in all supported browsersInformed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
- ~~Label as security and @ mention
@gitlab-com/gl-security/appsec
~~ The MR includes necessary changes to maintain consistency between UI, API, email, or other methodsSecurity reports checked/validated by a reviewer from the AppSec team
Edited by drew stachon