Decide where the work belongs
Identify the decision at risk
Name the workflow that relies on the detail result, such as reconciling a total or reviewing an exception. Record whether the parent number is merely informative or serves as a gate, and state what a misleading child population could cause someone to conclude.
Estimate affected surfaces
List the cards, tables, saved views, and date or segment combinations that share the drilldown contract. Use observed examples and report definitions rather than guessed usage volume. A narrow, high-consequence card may outrank a broad view used only for exploration.
Choose a queue outcome
Place the case in a repair, definition review, or documentation queue. Set the next artifact: a scope contract, a fixture, or a copy change. Add an owner who can decide whether inheritance and grouping should be preserved.
What to carry forward
Prioritize the issue when a known decision depends on a child result whose scope is wrong or unexplained. Queue definition review first when intent is ambiguous; queue implementation when the intended relationship is documented and the observed child constraints violate it.
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