Keep the lesson for the next incident
Document the total’s population and rule
State whether totals sum displayed cells or recompute a measure over underlying records, and explain how filters or hidden categories affect the population. Keep non-additive cases explicit. A reader should be able to understand why a total differs from cell arithmetic without needing to inspect the query or infer the aggregation grain.
Retain a discriminating total fixture
Keep unequal groups, overlapping identities, or ratios with distinct denominators as appropriate to the original defect. Record independent cell and total calculations, including the tempting wrong alternative. Explain why the difference matters so later fixture simplification does not turn the case into an ordinary sum that no longer exposes the semantic boundary.
Review measure and visibility changes
Assign review when total expressions, grouping, display filters, or export logic change. Compare the small fixture through the affected surfaces. Track unclear-total feedback separately from proven arithmetic defects while preserving links between them, since a correct calculation may still need a clearer label to support the reader’s intended decision.
What to carry forward
Close with an explicit total definition, a readable non-additive fixture, and an owner for measure or visibility changes. Preserve limits on supported comparisons. The next maintainer should be able to explain the total from its source population rather than assuming that adding visible cells is always the most trustworthy interpretation.
Technical background: Google Cloud documentation.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow