Aglet

Prioritize result sort expectations with a clear user decision

Sort work matters when people make a choice from an order they cannot interpret or when the default hides the result they expected. Compare label, default, and rule changes before a ranking rewrite. A scoped copy correction may restore trust without changing valid business ordering.

Decide where the work belongs

  1. Name the decision affected

    Describe what a person is trying to compare and why the current order changes that decision. Compare search, category, and return contexts. Keep a one-off surprising row distinct from a default that misleads every query.

  2. Compare remedies

    Set sort-label copy, default selection, explicit promotion treatment, ranking change, and category scope beside one another. Consider reversibility and the risk of moving useful results. Prefer a repair that makes the ordering reason visible.

  3. Choose a bounded move

    Record owner, route and query scope, and revisit evidence. Decide whether to investigate order, clarify copy, or test a new default. Preserve before-state examples so the queue position can be reviewed after a change.

What to carry forward

Prioritize the order or label that changes a meaningful search comparison and cannot be explained from the visible control. The decision should name scope and remedy. If the order is intentional and legible, leave it and queue a different result issue only with evidence.

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