Establish what is happening
Name the expected content
Record page, project or workspace, role, filters, time range, and the record or action the user expected. State whether the expectation came from a previous result, navigation label, setup promise, or personal assumption.
Compare empty causes
Check no data, no matching filters, unavailable scope, pending processing, and incomplete setup using safe fixtures. Capture the first observable difference and avoid treating all zero counts as the same state.
Bound the blocked decision
Describe whether users need to create, connect, clear, wait, request access, or simply move on. Note whether the page offers a truthful next step or sends them to an unrelated destination.
What to carry forward
Triage should state expected content, actual empty cause, current filters or role, blocked decision, and evidence gaps. Escalate when users cannot tell whether to act or wait; otherwise classify a scoped copy or navigation gap. Record the exact query, role, project, lifecycle state, and data presence behind the empty result, then distinguish no records from no matches, setup, pending, or unavailable scope.
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