Keep the lesson for the next incident
Document the ordering contract
State which raw key defines chronology, how periods are grouped, and which explicit ranking options are supported. Explain how saved and shared views retain the choice. Keep display labels outside the ordering rule unless text order is actually the intended task, rather than relying on a convenient formatted string as a universal key.
Retain a cross-boundary sequence
Keep periods that expose alphabetic month order, numeric text order, or repeated labels across years as relevant to the defect. Record chronological and deliberate ranking expectations independently. Explain why a short ordinary range is insufficient so future fixture simplification does not remove the one boundary that distinguishes the competing sort behaviors.
Review formatting and saved-state changes
Assign review when date labels, period grouping, sort selectors, rendering, or exports change. Compare the discriminating sequence across affected surfaces. Track confirmed ordering defects separately from missing-period data issues while preserving their distinction in guidance, since both can make a timeline look wrong but require different evidence and corrections.
What to carry forward
Close with explicit time-key semantics, a readable cross-boundary fixture, and an owner for sort or formatting changes. Preserve any unsupported period format in guidance. The next maintainer should be able to change a date’s presentation without changing its chronological position or erasing a reader’s deliberate ranking choice.
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