Skip to content

Improve command palette metrics tracking 8

What does this MR do and why?

places results

  • User clicks "Explore" in Places
  • User clicks "Preferences" in Places
  • User clicks "Profile" in Places
  • User clicks "Your work" in Places

scope related results

  • User searches in project scope when option is available
  • User clicks group search scope when option is visible
  • User clicks "in all GitLab" in command palette

This is a part of large set of internal events we are adding to command palette and global search.

Here is a spreadsheet of all events and requested data to be collected Google Sheet.

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. Make sure advanced search is installed and enabled
  2. Make sure you enable zoekt.
  3. In terminal run
    rails runner scripts/internal_events/monitor.rb click_all_gitlab_scoped_search_to_advanced_search
    rails runner scripts/internal_events/monitor.rb click_explore_in_command_palette
    rails runner scripts/internal_events/monitor.rb click_group_scoped_search_to_advanced_search
    rails runner scripts/internal_events/monitor.rb click_preferences_in_command_palette
    rails runner scripts/internal_events/monitor.rb click_profile_in_command_palette
    rails runner scripts/internal_events/monitor.rb click_project_scoped_search_to_advanced_search
    rails runner scripts/internal_events/monitor.rb click_your_work_in_command_palette
  4. On any gitlab page press '/'
  5. Search for any merge_request, click result
  6. Watch the terminal to indicate the hit

Related to #438845 (closed)

Edited by Tomas Bulva

Merge request reports