Growth/Engineering/Incident tracking

This page tracks "incidents", meaning notable, user-facing bugs, for code in GrowthExperiments. We are tracking these to assess frequency of issues and decide what/how we need to adjust practices in response, not to cast judgment or blame.

Criteria for adding tasks:

Criteria for low/medium/high:
 * would have blocked the train, but fixed in advance
 * blocked the train
 * incorrect/missing analytics for Growth features
 * significant performance change


 * high: blocked train, caused outage in production
 * medium: ?
 * low: ?