Pipeline Execution frontend instrumentation for data tracking
Proposal
We need to instrument some data tracking in order to inform an Ops Section-Wide JTBD. The following are different events we need to track:
Test Widget Events
We would benefit from having two events tracked for test widgets: tracking the click to expand the widget and the clicks on the individual job logs would be the most beneficial. Tracking the clicks on expanding the widget is what the main ask is, but often, users can just be clicking around to see what certain features do. Tracking the clicks on individual job logs can imply usage of the Test Widget that leads to a commit.
Test Tab
We would benefit from tracking the clicks on the test tab - I suggest having one event that will track clicks from both the Full Report
link and the Test
tab would be beneficial as they lead to the same page. I don't foresee a situation where we would need to differentiate between these clicks unless we were trying to establish a funnel of events for a particular user. I would be open to having separate events for each the Full Report
link and Test
tab, but one event that tracks both would be fine for the purposes of this analysis.
Failed Jobs
This would be a great add to our JTBD! There are two main parts of this we should add tracking to: clicking on the Failed Jobs
tab and tracking the retry, but @jivanvl's work would include adding tracking to the retry component so we would only need tracking for clicks on the Failed Jobs
tab.