Decide where the work belongs
Identify blocked decisions
Name comparisons or actions that require exact code identity: associating a regression, reviewing a release boundary, or confirming which version served traffic. Give higher priority when the ambiguity affects an active customer path.
Estimate context value
Compare the effort of recovering the reference with the harm of leaving the release unclassified. Existing release notes, build records, or runtime markers may provide enough value without requiring broad reconstruction.
Set a recovery checkpoint
Choose a concrete point before the next release review, verification result, or recurrence analysis. State the evidence that would close the gap and what temporary label keeps downstream readers from treating it as resolved.
What to carry forward
The queue decision should identify the blocked release decision, an owner, and a recovery checkpoint. Keep priority high when unknown commit identity could misattribute a customer-facing regression; otherwise schedule metadata recovery alongside the next relevant review.
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