Keep the lesson for the next incident
Compare recurring rows
Align browser engine, version, operating system, viewport, input, state, application revision, and first divergent boundary across episodes. Keep distinct failures separate when only the browser label repeats.
Preserve the matched fixture
Document the task, data shape, expected completion, and comparison browser needed for a meaningful future run. State which environment conditions are essential and which are incidental.
Define compatibility recurrence
Set a review trigger for the same engine boundary after browser, layout, storage, or input changes. Name the owner and the minimum matrix that must be checked before release confidence is stated.
What to carry forward
The lesson should preserve one targeted compatibility matrix and a recurrence rule for the observed boundary. Treat it as provisional until later browser changes show the workflow remains complete across the reviewed contexts. Keep a browser matrix for the workflow, known rendering or input boundary, and last review date, and revisit it after platform, CSS, navigation, or form changes.
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