Experiment: no personal trials, only group trials
What does this MR do?
Addresses #215852 (closed).
We want to experiment with the idea of only allowing trials on group namespaces and stop allowing trials on personal namespaces. If the user does not have any groups, we should show them a field for “Group name” so they can create a new group to start the trial on. Otherwise, they will pick from a list of their existing groups and have the option to “Create group.”
Why no changelog entry?
As this is an experiment and all code is behind a feature flag, we will not post any changelog entries at this time. If the experiment proves successful and we incorporate this into our normal flow, we will add a changelog at that time.
Why no documentation?
Same reason as the changelog entry. If & when this gets fully incorporated as the default flow, we’ll update any associated documentation at that time. Although, there is currently a push to include documentation updates with
Screenshots
| Before | After |
|---|---|
 |
 |
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