Setup tracking for pipeline index page actions

Problem

To understand the JTBDs related to pipeline index page, we need the answers to the following questions:

1. What are the most performed actions?
2. What are the least performed actions?
3. Where are users navigating to Pipeline index page from?
4. Where do users go to from Pipeline index page?

Proposal

Set up data tracking for the actions users perform on the pipeline index page so we're able to triangulate the information from the qualitative research with the data and make better decisions to declutter the page.

Structured Snowplow events to track

• Category: The page or backend area of the application. Unless infeasible, please use the Rails page attribute by default in the frontend, and namespace + classname on the backend. If you're not sure what it is, work with your engineering manager to figure it out.
• Action: A string that is used to define the user action. The first word should always describe the action or aspect: clicks should be click, activations should be activate, creations should be create, etc. Use underscores to describe what was acted on; for example, activating a form field would be activate_form_input. An interface action like clicking on a dropdown would be click_dropdown, while a behavior like creating a project record from the backend would be create_project
• Label: Optional. The specific element, or object that's being acted on. This is either the label of the element (e.g. a tab labeled 'Create from template' may be create_from_template) or a unique identifier if no text is available (e.g. closing the Groups dropdown in the top navbar might be groups_dropdown_close), or it could be the name or title attribute of a record being created.
• Property: Optional. Any additional property of the element, or object being acted on.
• Value: Optional, numeric. Describes a numeric value (decimal) directly related to the event. This could be the value of an input (e.g. 10 when clicking internal visibility)

Label	Action	Image
pipelines_table_component	click_manual_actions
pipelines_table_component	click_retry_button
pipelines_table_component	click_artifacts_dropdown
pipelines_table_component	click_cancel_button
pipelines_table_component	click_ci_status_badge
pipelines_table_component	click_pipeline_id
pipelines_table_component	click_commit_sha
pipelines_table_component	click_mr_ref
pipelines_table_component	click_minigraph
pipelines_table_component	click_commit_title
pipelines_filtered_search	click_filtered_search
pipelines_filter_tabs	click_filter_tabs

Snowplow event tracking checklist

• Engineering complete work and deploy changes to GitLab SaaS
• Verify the new Snowplow events are listed in the Snowplow Event Exploration dashboard
• Create chart(s) to track your event(s) in the relevant dashboard
  • Use the Chart Snowplow Actions SQL snippet to quickly visualize usage. See example