Build a useful investigation brief
Trace project creation
Map the create-project submission, response, redirect, project identifier, and setup state. Confirm the page loads the project in the intended workspace. Record validation or authorization outcomes and keep any one-time test-key value out of logs and evidence.
Follow setup records
Create a synthetic test key and run the built-in check through the documented path. Compare key metadata, queued sample status, saved Signal, and linked Work Item with the page. A missing record, delayed state, or filtered query is a possibility to distinguish with evidence.
Inspect empty-state boundaries
Compare owner and restricted views, new and established projects, and a project with no sample evidence. Check whether the empty-state action points to the same project context and whether back navigation returns to the correct workspace. Note unsupported producer or external states explicitly.
What to carry forward
The investigation is ready when project creation, redirect, setup records, sample result, and empty-state query can be followed for one synthetic journey. Deliver the first divergence and preserve the distinction between a local built-in sample and any untested external data path.
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