Check whether the outcome improved
Check a single-project group
Review several events for one project and confirm labels, summary, actions, and destination remain compact but specific. Open an item and return. Record the project identity a person can see before acting.
Check a cross-project near match
Review similar events from two projects with one shared actor or event type. Confirm they remain separated or visibly labeled. Test a child action and ensure its destination retains project context.
Review summary and return
Inspect direct links, narrow layout, empty group, and late event behavior. State tested workspaces and omitted platforms. Leave a partial pass when permissions or child actions are not directly observable. Test the same summary when project names have similar wording.
What to carry forward
Verification passes when related events group within the right project boundary, near matches remain attributable, and destinations preserve context. If a workspace or device path is untested, document it. A count of grouped items cannot replace readable project identity.
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