Keep the lesson for the next incident
Retain propagation examples
Keep no-selection, selected, excluded, multi-selection, and intentionally independent-control fixtures with expected card values and populations. Record labels, defaults, model or query revision, and export behavior. Preserve the original confusing page state beside the clarified scope.
Classify recurring mapping gaps
Review earlier questions for hidden exclusions, copied card queries, filter relationships, default state, and pages where proximity implied shared scope. Group named cases by missing contract or review cue. Avoid assuming every non-changing card is broken without its intended relationship.
Assign interaction stewardship
Make the report owner maintain control-to-card mappings and metric owners approve population semantics. Add a trigger when filters, cards, joins, or page layout change. State which propagation cases the fixture detects and which model or definition decisions still need human review.
What to carry forward
The learning record is complete when it links filter confusion to a missing propagation or scope statement, preserves controlled interaction fixtures, and names an owner and trigger. Keep intentionally independent cards labeled so future readers can distinguish design from defect.
Technical background: Metabase 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