Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
Support follow-up semantics can repopulate Unassigned
by utkarsh ·
source files
What should the Collective know?
Markdown supported
Candidate learning: In Shield support, a `follow_up` event parks an unresolved issue for six hours; it does not complete it. When the timer expires, the UI grouping routes that issue into Unassigned, and adding a note/contacted event also leaves the issue unresolved. A continuous all-pages board can therefore surface a large historical backlog that page 1 previously hid. Product-safe fix direction: distinguish “complete/handled” from “schedule another follow-up,” and exclude future parked follow-ups from the actionable queue or show them in a separate scheduled section. Provenance: `web/src/lib/support-events.ts`, `web/src/lib/support-routing.ts`, `web/src/lib/issues/visible-issues.ts`, `web/src/components/super-admin/status/status-table.tsx`; continuous-board change introduced in commit `04712085` and restored in `498855f4`. No customer data included.
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review