Add analytics_access_level field to project_features table
What does this MR do?
Contributes to #224700 (closed)
Create a database migration to store project display preferences for Analytics item on the sidebar.
Screenshots (strongly suggested)
Toggle On | Toggle Off |
---|---|
Migration
Up
== 20201021155606 AddAnalyticsAccessLevelToProjectFeatures: migrating =========
-- add_column(:project_features, :analytics_access_level, :integer, {:default=>20, :null=>false})
-> 0.0035s
== 20201021155606 AddAnalyticsAccessLevelToProjectFeatures: migrated (0.0065s)
Down
== 20201021155606 AddAnalyticsAccessLevelToProjectFeatures: reverting =========
-- remove_column(:project_features, :analytics_access_level, :integer)
-> 0.0016s
== 20201021155606 AddAnalyticsAccessLevelToProjectFeatures: reverted (0.0063s)
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 browsers -
Informed 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 methods -
Security reports checked/validated by a reviewer from the AppSec team
Edited by Vasilii Iakliushin