Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 34,936
    • Issues 34,936
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1,256
    • Merge Requests 1,256
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLabGitLab
  • Merge Requests
  • !46746

Merged
Opened Nov 03, 2020 by Miranda Fluharty@mfluharty☘Developer3 of 10 tasks completed3/10 tasks

Track browser performance widget expansions

  • Overview 18
  • Commits 2
  • Pipelines 15
  • Changes 7

What does this MR do?

For more context, see #224603 (closed)

This MR adds a new usage ping event (i_testing_web_performance_widget_total) that tracks the number of unique users per instance that expand the browser performance MR widget.

Per the Usage Ping Guide, this MR adds a new feature flag (usage_data_i_testing_web_performance_widget_total) which is enabled by default, and the event is only tracked when the feature flag is enabled.

Rather than adding specs for this to the already-too-large ee_mr_widget_options_spec.js, I made the browser performance MR widget into its own component and added the spec there. This way, we can start moving the browser performance logic into the component and moving the related specs into a dedicated file.

Screenshots

Event tracking request from the network panel (gdk):

Screen_Shot_2021-01-12_at_15.21.05

Does this MR meet the acceptance criteria?

Conformity

  • Changelog entry
  • Documentation (if required)
  • Code review guidelines
  • Merge request performance guidelines
  • Style guides
  • Database guides
  • Separation of EE specific content

Availability and Testing

  • Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
  • Tested in all supported browsers
  • Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Edited Jan 13, 2021 by Miranda Fluharty
Assignee
Assign to
Reviewer
Request review from
13.8
Milestone
13.8 (Past due)
Assign milestone
Time tracking
Reference: gitlab-org/gitlab!46746
Source branch: 224603-track-browser-performance-widget-expansions

Revert this merge request

This will create a new commit in order to revert the existing changes.

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.

Cherry-pick this merge request

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.