Decide where the work belongs
Assess active exposure
List environments, cohorts, traffic, and customer paths that may be on the pending version. Give higher priority when exposure is broad, increasing, or impossible to identify from the current records.
Assess decision blockage
Name whether the stalled state blocks expansion, verification, incident response, or release communication. A blocked verification with stable exposure may differ from an unknown rollout serving critical traffic.
Choose a checkpoint
Set a time or event for the next review, such as a fresh status record, expected transition, or owner confirmation. State what evidence would move the item forward or require a separate investigation.
What to carry forward
The queue result should name the exposure uncertainty, blocked decision, responsible reviewer, and checkpoint. Keep the item urgent while the current version or rollout boundary is unknown; lower priority only when evidence shows stable, bounded exposure. A known held rollout may need a scheduled review, while unknown exposure needs faster evidence because the team cannot tell which version customers receive or how to recover.
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