Aglet

Triage result sort expectations before changing ordering

People read relevance, newest, price, and category position as different promises. Triage the ordering contract before changing ranking. Capture query, selected sort, default state, filters, business rules, and result positions so an intentional policy is not mistaken for a broken control.

Establish what is happening

  1. Capture the sort state

    Record query, route, selected sort, default, filters, result order, and any promotion or category context. Include an explicit sort and a default search. Keep the URL or request inputs attached to the result sample.

  2. Compare visible promises

    Write what the label implies and what the order appears to use. Compare relevance, date, price, position, and promoted placement. A result can be correctly sorted within a category while surprising someone who expects global relevance.

  3. Set the ordering boundary

    State which contexts, labels, and exceptions are in scope. Preserve a query where the sort behaves as expected. Stop when the team can name whether the issue is order, copy, default selection, or an unresolved policy tradeoff.

What to carry forward

The triage output is a sort contract naming input, context, default, and visible result order. Stop when another reviewer can reproduce the promise. If business placement intentionally changes order, route labeling or grouping separately from a generic relevance complaint.

Technical background: Elastic 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