Keep the lesson for the next incident
Keep the project evidence
Record workspace, project, resource, actor, event, group key, summary, action, and destination. State which identity mattered. This keeps a grouping lesson from becoming a vague warning about “too much context.”
Compare later groups
Review another shared actor, event type, project, and direct action after the change. Look for a summary that still hides ownership or a destination that opens the wrong context. Preserve a successful single-project control.
Refine one context check
Require future reviews to pair a single-project group with a cross-project near match and open one child action. Assign ownership and revisit date. Define the observation that would show grouping reduced noise without weakening attribution. Preserve a case where the project boundary stayed obvious.
What to carry forward
The learning record connects one attribution error to later project evidence and a repeatable grouping-context check. Stop when another reviewer can apply it to a new workspace. Carry forward uncertainty where platform summaries or access context are not fully observable.
Technical background: Android developer documentation.
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