Fix tier for instance and group DevOps Adoption
What does this MR do?
The DevOps Adoption features, which exist at both the instance and group levels, are intended to be Ultimate features (according to epic and documentation). This moves them out of the Starter list and into the Ultimate list.
This was prompted by @pshutsin's observation in #326008 (comment 557625793).
Corresponding issue: #329177 (closed)
Does this MR meet the acceptance criteria?
Conformity
-
📋 Does this MR need a changelog?-
I have included a changelog entry. -
I have not included a changelog entry because "Any change behind a feature flag disabled by default should not have a 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 Dan Jensen