CTA Link update for DuoPro widget variation
What does this MR do and why?
- Updates CTA link per issue discussion / product requirements
- Updated spec to match
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.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
| Before | After |
|---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
-
Setup gdk to simulate SaaS - https://docs.gitlab.com/ee/development/ee_features.html#simulate-a-saas-instance and restart GDK.
-
Sign in. Create new group.
-
In rails console create / update new GitLab subscription for your new group:
bin/rails c namespace = Group.last gitlab_subscription = namespace.gitlab_subscription # find or create a new one if needed gitlab_subscription.update(hosted_plan: Plan.find_by(name: 'premium'))
-
To test Duo Pro
bin/rails c add_on_purchase = GitlabSubscriptions::AddOnPurchase.create(subscription_add_on_id: GitlabSubscriptions::AddOn.find_by(name: 'code_suggestions').id, namespace: Group.last, started_at: 61.days.ago, expires_on: (Date.today + 1), trial: true, quantity: 1, purchase_xid: '1', organization_id: 1)
-
To test trial end period + progress bar - modify trial start / expiration values for AddOnPurchase accordingly and test link paths
Related to #485845