Ultimate Trial Status widget is oscillating between displaying 1 and 2 CTAs

Summary

Our Ultimate Trial Status widget is oscillating between displaying 1 and 2 CTAs. It should display 2 at all times.

Steps to reproduce

  • Login to a Production namespace that has an active trial.
  • Hover over the Ultimate trial status widget at the top of the left hand side nav. The widget will likely display one CTA (compare all plans)
  • Refresh the page. Both CTAs (either Upgrade to Ultimate and Compare All Plans - control; Contact Sales and Compare all plans for the current running 80/20 Active trial status connect with Sales experiment) will appear.
  • Take your cursor elsewhere, the widget will close. Leave for 10-15 seconds
  • Revisit the widget and one CTA will appear.

🎥 Loom video of recorded behavior.

Example Project

What is the current bug behavior?

The widget is inconsistently displaying one then two, then one CTA over the same session. This has been observed on Staging and Production.

Staging - SaaS Trial group/namespace (5 days old) Production - SaaS Trial group/namespace (25 days old)

What is the expected correct behavior?

Two CTAs - either Upgrade to Ultimate and Compare All Plans - control; Contact Sales and Compare all plans for candidate experience - should appear consistently together.

Relevant logs and/or screenshots

Screen_Shot_2022-02-07_at_11.25.01_AM

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info 
(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


(we will only investigate if the tests are passing)

Possible fixes

Edited by Serhii Yarynovskyi