Establish what is happening
Capture the parent state
Record the card title, metric definition, selected period, visible filters, grouping, and clicked value exactly as shown. Save a representative row or aggregate from the parent so later comparisons use the same state rather than a remembered screen.
Compare child constraints
Inspect the detail view for each inherited filter, date boundary, dimension, and row limit. Mark every constraint that disappeared, appeared, or changed meaning. A changed grouping can explain a different row count even when the underlying population is unchanged.
Name the question change
Write one sentence describing what the child view answers and how that differs from the parent question. Separate an expected decomposition from a scope defect, and record any unresolved intent with the report owner before prioritization.
What to carry forward
Triage is complete when the click path, parent state, child constraints, and intended relationship are recorded. If the product contract does not say whether a control drills into records, a subgroup, or a filtered aggregate, classify the case as an unresolved definition decision.
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