Establish what is happening
Collect the comparison evidence
Place the reports side by side with submission time, source, product area, account context, release information, and any reproduction detail. Record stable references instead of copying sensitive message content into a new note, and mark which fields are missing.
Separate outcome from wording
Compare the requested customer outcome and observed behavior, not just matching nouns. A checkout failure and a receipt delay may share a payment term while requiring different owners. Keep reports separate when versions, permissions, or triggers materially differ.
Choose a safe grouping boundary
Select a canonical review record only after the equivalence test passes. Link related entries, retain their customer and channel counts, and document exceptions such as a second regression with the same visible symptom. Do not erase or overwrite source evidence.
What to carry forward
The useful output is a linked duplicate set with one stated customer outcome, preserved evidence references, and an explicit exception list. If equivalence remains uncertain, leave entries separate and flag the missing comparison detail for follow-up rather than presenting a false single issue.
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