Skip to content

Experiment Cleanup: promote_ultimate_features

What does this MR do and why?

Basically revert !136199 (merged), and database clean up will happen in future MRs.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

How to set up and validate locally

  1. Setup to simulate SaaS and restart GDK
    • Make sure Admin > Settings > General > Sign Up Restrictions match: no admin approval, but hard email confirmation
  2. Register as a new user.
  3. Confirm email by finding the confirmation path from last User created in rails console
    • Rails.application.routes.url_helpers.user_confirmation_path(confirmation_token: User.last.confirmation_token)
  4. Visit the path from the previous step.
  5. You should be on the sign in page, log back in.
  6. Select any 'role' and 'Just me' in the welcome form after sign up step.
  7. Choose 'Create a new project'
  8. Click 'Continue'
  9. Fill out fields to create a group and project on the next page.
  10. Click 'Create project'
  11. Verify you get to the onboarding and page refreshes to provide a "Ok, let's go" button.
  12. Click on "Ok, let's go" and verify you are dropped into created project's learn gitlab page and observe the tasks links

Related to #440838 (closed)

Edited by Roy Liu

Merge request reports