Decide where the work belongs
Name the attribution cost
Describe what action or owner becomes unclear when projects combine. Compare same actor across projects, same resource across workspaces, and same event type with different destinations. Keep an overloaded list separate from a wrong-context group.
Compare grouping scopes
Set project, workspace, resource, actor, date, and separate notifications beside one another. Consider summary, child labels, permissions, and return links. Prefer a scope that reduces duplicate attention without making a person reidentify the project.
Choose a bounded move
Record project class, owner, and revisit evidence. Decide whether to change key, summary, label, or destination. Preserve the current groups and a clean single-project control so the tradeoff can be reviewed.
What to carry forward
Prioritize cross-project changes where grouping hides ownership or sends actions to the wrong destination. The decision should state preserved project identity and remedy size. If grouping is clear and noise is low, prioritize a more specific notification issue instead.
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