Expose some free users to new purchase flow
What does this MR do?
Expose a portion of free gitlab.com users to the new purchase flow:
Reviewing steps: Enable feature flags on a gitlab.com environment with groups on a free plan
Feature.enable(:free_group_new_purchase_flow)Requirements
-
Target: Owners on billing page for groups with a free plan -
The control free group owners that select to upgrade on a group billing page will be sent to the existing checkout funnel. The experiment free group owners that select to upgrade on a group billing page will be sent to the new checkout funnel https://gitlab.com/-/subscriptions/new -
For experiment group upgrade dropdown in the checkout flow with the name of the group from which they clicked the upgrade button. For example, if I'm a member of 3 groups, one with the name XYZ. If I click "upgrade" from the group billing page of groupXYZthen in the checkout funnel the question regarding where the subscription should be applied (question titled: "GitLab Group") should be prefilled with my groupXYZ.
Issue #211423 (closed)
Screenshots
| Control | Experiment |
|---|---|
 |
 |
 |
 |
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 Alper Akgun