Aglet

Verify closure or renewal of stale customer feedback

State transitions on old feedback need stronger explanation than simply past due. Verification should exercise the current workflow or the new evidence path, confirm links and counts, and make sure the historical request remains discoverable after the decision. Verification should preserve the historical request while proving what the current product does.

Check whether the outcome improved

  1. Check the chosen state

    Apply the closure, renewal, merge, or active rule to the current evidence. Confirm the state reason names a real behavior or evidence change and does not rely solely on age, silence, or a renamed feature.

  2. Audit continuity

    Follow links from the historical request to newer feedback, implementation work, or verification results. Reconcile counts and dates where a merge occurred, and ensure no active customer context disappears when the record changes state.

  3. Exercise future review

    Confirm the revisit date, owner, or trigger is visible and actionable for the chosen state. If current evidence is incomplete, verify that the record says provisional rather than presenting the stale request as resolved.

What to carry forward

Verification passes when the state change matches current evidence, historical continuity remains auditable, and a future trigger exists where uncertainty remains. If current behavior was not checked, keep the request in refresh or provisional status instead of claiming 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