Skip to content

feat(tickets): CU-86ajn8n1y reapply board activity indicators and filter - #350

Open
romanivan-flamingo wants to merge 11 commits into
mainfrom
hotfix/reapply-tickets-board-staleness
Open

romanivan-flamingo wants to merge 11 commits into
mainfrom
hotfix/reapply-tickets-board-staleness

Conversation

@romanivan-flamingo

@romanivan-flamingo romanivan-flamingo commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

Summary

Revert of the landed revert #348 (1374bb6) - restores #155 in full (30 files): activity/staleness card indicators, the activity board filter, lastActivityAt/activityState selections, staleAfterMinutes on statuses, sidecar docs. Now on current main with core lib ^0.0.608 (the reapply lib release from openframe-oss-lib#2103).

Testing flow

The pr-350 image is deployed to the joint feature tenant (BE reapply branch feature/ticket-activity-v2, openframe-saas-tenant#3038) for end-to-end testing of the reapplied feature (FE + lib 0.0.608 + BE openframe-oss-lib#2099).

Merge after the feature-tenant testing passes - merging returns the feature to main.

🤖 Generated with Claude Code

Revert of the landed revert (1374bb6, #348) - restores #155 in full
(30 files: indicators, staleness, activity filter, sidecar docs).
Ships for testing together with the lib reapply branch
(hotfix/reapply-board-card-activity-indicators) and BE reapply
openframe-oss-lib#2099.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@michaelassraf

Copy link
Copy Markdown
Contributor

romanivan-flamingo and others added 2 commits September 8, 2026 11:12
…0.0.608

Reapply lib release (openframe-oss-lib#2103) - BoardTicket.activity is
back in the lib; unblocks this reapply branch on top of current main.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@romanivan-flamingo
romanivan-flamingo marked this pull request as ready for review September 8, 2026 09:19
@romanivan-flamingo
romanivan-flamingo requested review from a team as code owners September 8, 2026 09:19
romanivan-flamingo and others added 7 commits September 16, 2026 11:32
…onnect. CU-86akjcwb3

Three delivery-reliability fixes in the live bridge:
- a CREATED arriving before the drawer connection exists no longer drops
  silently: the node is written and a throttled first-page refetch lists it
- redelivered pushes dedup by the stable notification id: a CREATED for an
  already-read row refreshes fields without resurrecting it, and the unread
  count bumps only when an edge is actually inserted
- on NATS reconnect the first page and unread counts are re-pulled, closing
  the no-replay gap until notifications ride a JetStream stream

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…environment. CU-86akjcwb3

Review follow-ups, plus the reconnect comment now states the decision: the
DB-backed refetch is the permanent recovery mechanism - no JetStream replay.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…andler-hardening

# Conflicts:
#	src/app/components/notifications/notifications-data-provider.tsx
…s-board-staleness

# Conflicts:
#	package-lock.json
#	package.json
#	src/app/(app)/tickets/components/.tickets-view.md
#	src/app/(app)/tickets/components/tickets-filter-modal.tsx
#	src/app/(app)/tickets/components/tickets-view.tsx
#	src/app/(app)/tickets/queries/.ticket-queries.md
#	src/app/(app)/tickets/services/.ticket-service.md
#	src/app/(app)/tickets/services/.ticket-service.types.md
#	src/app/(app)/tickets/utils/.query-keys.md
…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>
…suppression' into hotfix/reapply-tickets-board-staleness
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