Fix a tracking event that stopped firing after a UI change
An event that broke when the component around it changed, fixed and pinned by a browser check.
The ticket
Repair a tracking event that stopped firing and add a check that catches it next time.
Acceptance criteria
- The event fires again with its expected properties
- A browser check captures it and asserts the payload
- The check runs in CI so the next redesign breaks the build
- The gap in the data is noted for anybody reading the historical numbers
What lands as proof
A browser check capturing the outbound event, which is the first automated assertion this event has ever had.
Why teams defer it
- The dashboard keeps rendering, just with a line that quietly flattens.
- Whoever changed the component had no way to know an event depended on it.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: repair a tracking event that stopped firing and add a check that catches it next time. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means the event captured in a browser check, before and after, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- None is required before the run starts. Every claim this ticket makes can be checked by machine, so the agent works straight through and a person reviews the finished pull request like any other.