Decide where the work belongs
Rate evidence freshness
List the age and source of each supporting signal, then identify recent corroboration or evidence that contradicts it. Do not convert a lack of recent reports into proof that the problem ended, especially when reporting coverage changed.
Compare present cost
Estimate current reach, consequence, workaround, and recurrence using only available evidence. Consider whether product changes make the old request easier, harder, or irrelevant. Keep assumptions explicit so a reviewer can challenge them.
Decide refresh versus delivery
Choose whether to investigate current state, schedule a fix, merge with a newer request, or archive. Record the trigger and date for revisiting the choice. Give evidence refresh its own queue position when implementation cannot yet be justified.
What to carry forward
The decision should show current cost, evidence freshness, product context, and whether the next action is refresh or delivery. Stop when the queue records a reasoned state and revisit trigger; retain uncertainty when recent coverage is too thin to support closure.
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