Establish what is happening
Capture project context
Record workspace, project, resource, actor, event type, timestamp, group label, summary, and destination for similar notifications. Include two projects with a shared actor and one project with several resources. Keep ownership visible.
Compare what is shared
Ask whether events share a resource, project, workspace, actor, or only a time window. Compare summary wording and action context. A common event type is not enough if the next decision belongs to different owners.
Set the grouping boundary
State which project or workspace identity must remain in every group, what may combine, and how a person returns to one project. Preserve a separate control. Stop when another reviewer can predict attribution from the summary.
What to carry forward
The triage output is a cross-project boundary with retained project identity, grouping key, summary, and destination. Stop when shared activity and distinct work are distinguishable. If ownership context is missing, keep notifications separate and route the provenance gap.
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