Experiment: Pinned Navigation Items to Drive Team Activation

What does this MR do and why?

Full experiment context here: &18647

Testing whether adding key navigation items to the pinned menu by default will help new trial users discover theses areas of the product faster and therefore drive activation.

References

Screenshots or screen recordings

Before

After

How to set up and validate locally

bin/rails c

Feature.enable(:default_pinned_nav_items)

• Start up GDK to simulate SaaS with snowplow micro enabled
  • https://gitlab.com/gitlab-org/gitlab-development-kit/-/blob/main/doc/howto/snowplow_micro.md
  • https://docs.gitlab.com/ee/development/ee_features.html#simulate-a-saas-instance
    1. gdk config set snowplow_micro.enabled true
    2. reconfigure / restart if needed
• Sign out. Register a new user on a trial
  • For candidate users, select:
    • role "Software Developer"
    • reason for using gitlab: any of them except for "Learn the basics" or "Other"
• Create a group with a project.
• Visit the group or project
  • Verify the pinned items from the above screenshot exit
  • When clicking any of hte pinned nav items, frontend structured events are fired
    • click_pinned_menu_item
  • Open separate tab for snowplow: http://localhost:9091/micro/good
    • when pinning / unpinning nav items:
      • pin_menu_item
      • unpin_menu_item

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 #436965