Build a useful investigation brief
Map the context sources
Record how the current workspace is selected at the home, project, deep-link, and switcher routes. Compare displayed name, public identifier, and session context for one synthetic user. Keep route and membership evidence separate from the visible label a person sees.
Trace reads and writes
Open distinct synthetic projects and work items in each workspace, then perform an authorized create or update after switching. Compare the resulting record scope with the selected context. Stop and classify any unexpected record as an isolation finding, not a navigation quirk.
Test stale and parallel paths
Use an old project link, an unavailable workspace, back navigation, refresh, and two tabs with different contexts where supported. Record redirect, heading, selected workspace, and action destination. Note which stale states the app cannot control and keep them explicit.
What to carry forward
The investigation is ready when session context, route, membership scope, rendered records, and action destination can be compared for each workspace path. Deliver the first mismatch and preserve tenant and permission evidence as a separate finding from confusing navigation.
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