Decide where the work belongs
Rank workflow impact
Describe blocked completion, lost input, incorrect result, visual confusion, or degraded convenience. Give higher priority to account, save, checkout, or recovery paths than to cosmetic differences.
Rank audience evidence
Record observed browser and version coverage, device distribution if known, and whether the failing context is a required supported path. Keep unknown reach separate from an assumed market share.
Assess working alternatives
Compare equivalent paths in other browsers and any supported workaround. A workaround that changes the task or requires a different device should not erase the primary defect.
What to carry forward
The queue result should include workflow consequence, browser scope, reproduction confidence, owner, and a review point. Keep priority high when a required path consistently fails without an equivalent alternative. Rank the bug by affected users and blocked task, not by browser popularity alone; elevate it when a supported browser loses the primary path or reliable recovery.
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