Repository navigation
feat(aggregator): saved views — Drew-defined filters saved per person and shareable as URLs; default view persists #1276
Description
Part of epic #1184 (PM stack coherence — wave 2, 2026-10-26).
Every aggregator page currently offers at most one hard-coded filter (Area chips on /projects, grain chips on /roadmap). Drew's real questions are cross-cutting — "everything in nix that's blocked", "my epics this week", "fleet-ops in review" — and today each one is a fresh manual hunt across pages. Saved views let a filter set (repo, Area, Horizon, owner, canonical state, epic) be named, saved per person, shared as a URL that reproduces the view exactly, and set as a personal default that persists across visits. Views are stored dashboard-side like comments are (the aggregator's own store), operate over the canonical work-item projection, and render through the existing pages rather than forking new ones — a saved view is a parameterisation of Board/Projects/Roadmap, not a new surface to keep coherent.
Acceptance:
- A user can define a filter set (at least repo, Area, Horizon, owner, state), name it, and reopen it later with identical results.
- Every saved view has a shareable URL that reproduces the exact view for another signed-in viewer (or states plainly why it cannot).
- A per-person default view persists across restarts and applies on landing until explicitly cleared.
- Saved views survive a feed republish (they key on item identity, not render order) and are covered by tests.
Acceptance criteria
- A user can define a filter set (at least repo, Area, Horizon, owner, state), name it, and reopen it later with identical results.
- Every saved view has a shareable URL that reproduces the exact view for another signed-in viewer (or states plainly why it cannot).
- A per-person default view persists across restarts and applies on landing until explicitly cleared.
- Saved views survive a feed republish (they key on item identity, not render order) and are covered by tests.
Activity
developing-today commentedon Oct 27, 2026
CODE-400
dezren39 commentedon Oct 28, 2026
Intake review
Fleet-monitor intake pass (protocol §5), 2026-10-28. Still live: no merged or open PR references this issue (checked 2026-10-28T01:47Z); nothing has implemented it yet.
Related: part of epic #1184 (PM stack coherence, wave 2); siblings #1275 (command palette) and #1277 (bulk triage) share the canonical work-item projection this parameterises.
Notes / risks: the body's Acceptance list was already complete; the appended section restates it in criteria form. Risks: views keyed on render order or feed position would silently rot on republish — the criteria explicitly forbid that; and the shareable-URL path must degrade honestly for viewers who cannot see the same items. Priority normal, effort/m (store, URL encoding, default-view plumbing, tests).
Suggested approach: store views dashboard-side like comments, keyed on item identity; encode the filter set in the URL as the share format; land the default-view persistence last, behind the reopen-identical-results test.
39 remaining items
dezren39 commentedon Nov 2, 2026
agent-note:v1 — parked — OpenChamber scheduled lane
dezren39 commentedon Nov 2, 2026
agent-note:v1 — picked up — Lane E worker (task 4990)
queue/4990-1276-saved-views, and it was opened by a prior worker shift for this exact task. Per the fleet handoff infra note, dezren39 authorship is the fleet GitHub account, not Drew-ownership evidence. No hard-stop labels on feat(aggregator): saved views — Drew-defined filters saved per person and shareable as URLs; default view persists #1276 or PR feat(aggregator): saved views — named per-person filter sets, shareable URLs, persistent default (#1276) #4013.fix(aggregator): address Codex P2 findings on saved views (#1276)
Merge pull request #4013 from developing-today/queue/4990-1276-saved-…
dezren39 commentedon Nov 2, 2026
agent-note:v1 — done — Lane E worker (task 4990)