Make telephone optional on in-app trial forms
What does this MR do and why?
Make telephone optional on in-app trial forms
-
phone number should be optional, but still validate pattern.
-
make errors pretty - move away from default html5 form validation from browser.
-
aligned with the new user version of this form performed in Update the New User Registration Trial /company... (!188164 - merged)
Changelog: other EE: true
Screenshots or screen recordings
Click to expand
| item | Before | After | Video |
|---|---|---|---|
/-/trials/new |
![]() |
![]() |
Screen_Recording_2025-05-12_at_2.39.54_PM |
/-/trials/duo_enterprise/new |
![]() |
![]() |
Screen_Recording_2025-05-12_at_2.41.22_PM |
/-/trials/duo_pro/new |
![]() |
![]() |
Screen_Recording_2025-05-12_at_2.42.41_PM |
| general form validation updates | Screen_Recording_2025-05-12_at_2.49.54_PM | Screen_Recording_2025-05-12_at_2.50.36_PM | n/a |
How to set up and validate locally
Click to expand
- Setup gdk to simulate SaaS - https://docs.gitlab.com/ee/development/ee_features.html#simulate-a-saas-instance and restart GDK
Ultimate trial
- visit
/-/trials/newpath.
Duo Enterprise trial
- Create a new top-level group
- In the gitlab admin UI, edit the group to be on an ultimate plan(edit button from
http://gdk.test:3000/admin/groups) - visit
/-/trials/duo_enterprise/newpath.
Duo Pro trial
- Create a new top-level group
- In the gitlab admin UI, edit the group to be on a premium plan(edit button from
http://gdk.test:3000/admin/groups) - visit
/-/trials/duo_pro/newpath.
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Related to #527169
Edited by Doug Stull





