Skip to content

fix(tickets): suppress live notification popups for the on-screen ticket chat. CU-86ak4az87 - #414

Closed
romanivan-flamingo wants to merge 1 commit into
mainfrom
hotfix/ticket-chat-notification-suppression
Closed

romanivan-flamingo wants to merge 1 commit into
mainfrom
hotfix/ticket-chat-notification-suppression

Conversation

@romanivan-flamingo

Copy link
Copy Markdown
Contributor

What

Makes live-notification suppression symmetric between the Mingo drawer and the ticket details page (86ak4az87, parent 86ajn8hnd).

registerActiveDialogView (from @/lib/active-dialog-views) was called from exactly one place - the Mingo realtime hook. So a live message notification carrying a dialogId was suppressed (no popup) and auto-read while the Mingo drawer showed that dialog, but popped when the ticket details page showed the same client chat - the same event, two behaviours.

Fix: register the ticket's client-chat dialog (messageDialogId) as an active view while that chat is the visible pane, so isWatchingNotificationDialog in the notifications pipeline treats both surfaces alike. Done inside TicketNotificationsAutoReader (already the ticket page's notifications-concern component, already gated on clientChatOnScreen), so it is gated on the chat being on screen - not on mount - and the Details tab still alerts normally.

Testing

  • npm run type-check, ESLint (ci config), Prettier - clean
  • Registration is reference-counted and returns the unregister cleanup, so tab switches / dialog changes / unmount release it.

🤖 Generated with Claude Code

…ket chat. CU-86ak4az87

registerActiveDialogView was called only from the Mingo drawer, so a live
message notification for a dialog was suppressed and auto-read while the Mingo
drawer showed it, but popped on the ticket details page showing the same chat.
Register the ticket's client-chat dialog as an active view while that chat is
the visible pane, so isWatchingNotificationDialog treats both surfaces alike.
Gated on clientChatOnScreen, not mount, so the Details tab still alerts.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@romanivan-flamingo
romanivan-flamingo requested review from a team as code owners September 16, 2026 12:18
@michaelassraf

Copy link
Copy Markdown
Contributor

@github-actions

github-actions Bot commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

🦩 Flamingo Code Review

No findings on the current head.

Mode: advisory


Need another pass? Commits pushed after this review are not reviewed automatically.

  • Review the new commits — the commits added since this review
  • Review the whole diff again — ignoring what was already reviewed

Prefer typing? Comment @flamingo-review, or @flamingo-review full. To review every push on this pull request, add the flamingo-review-always label.

React 👍/👎 on inline comments to teach the reviewer.

Started 2026-09-16 12:18 UTC · updated 2026-09-16 12:18 UTC · workflow run

@romanivan-flamingo

Copy link
Copy Markdown
Contributor Author

Consolidated into #350: this branch's commits are now merged into hotfix/reapply-tickets-board-staleness (the single branch carrying the board-activity reapply + notification hardening #412 + this ticket-chat suppression), per the plan to keep 350 as the one branch. Closing here as redundant - the change ships via #350. CU-86ak4az87

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants