Establish what is happening
Locate the original boundary
Read the request's product area, expected outcome, affected context, and evidence date. Record what was known then and avoid reconstructing missing details from memory. Identify any linked work or decision that may have changed the situation.
Check current relevance
Compare the original workflow with the current product, release notes, support themes, and newer feedback available to the reviewer. Distinguish resolved behavior, renamed behavior, and an unchanged problem whose reports simply stopped arriving.
Choose a state with reasons
Keep active, refresh evidence, merge into a newer request, or archive only with a concrete reason and review reference. If customer harm may persist but evidence is old, route a bounded current-state check rather than closing silently.
What to carry forward
The output is a current-state triage record that preserves history, states what changed or remains unknown, and names the next owner or archive reason. Stop when age has been tested against present evidence; do not infer resolution from silence alone.
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