Decide where the work belongs
Rank the action that becomes unavailable
Describe the exact control or workflow that cannot progress while the task runs. Separate a brief delayed click from a freeze that prevents cancellation, navigation, or data entry. Give higher priority to a blocked primary workflow even when a secondary screen records a longer but harmless task.
Map reach across device and data shapes
Group reproductions by device class, browser version, viewport, account size, and triggering input. Mark which groups are confirmed, suspected, or untested. A narrow freeze may need a targeted queue item, while the same task across common groups supports immediate capacity.
Set a bounded queue decision
Choose immediate investigation, a scheduled slice, or a reproduction task that fills one missing dimension. Name the evidence that changes the decision, such as a stack trace on a representative device or a comparison after a recent release. Avoid treating a synthetic maximum as broad reach.
What to carry forward
Produce a queue decision that connects urgency to the blocked workflow and confirmed reach. Include whether the freeze is new, worsening, or longstanding, plus any missing device or data evidence. The decision is ready when the next engineer knows both the first reproduction to run and why it matters.
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