Decide where the work belongs
Rank current harm
Measure blocked actions, affected paths, users, environments, and trend using current evidence. Preserve the current impact even if the earlier episode was smaller or differently exposed.
Assess recurrence confidence
Compare symptom shape, release boundary, changed code or configuration, and recovery evidence from both episodes. Increase priority for strong matches; keep uncertainty explicit when only labels or timing align.
Set a durability checkpoint
Choose a review after the next correction and its full exposure or delayed window. Name the evidence that would show recurrence is prevented, merely hidden, or still unresolved.
What to carry forward
The queue result should combine current impact, recurrence confidence, owner, and durability checkpoint. Keep priority elevated when a prior fix lacked complete verification or the same customer path is failing again. Prioritize recurrence when the same customer path is affected or the prior fix cannot be shown in the current release; avoid urgency based only on similar wording.
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