Ship a Customer-Requested Feature This Week
Release saved dashboard filters by Friday and confirm that the customers who requested them can use the workflow end to end.
ContextFour customers asked to reopen the same filtered dashboard every morning. The smallest useful version saves a name and …
Four customers asked to reopen the same filtered dashboard every morning. The smallest useful version saves a name and the existing filter values; sharing and team-wide defaults stay out of this release.
ConstraintsNo new filter types, keep existing dashboard URLs working, and deploy behind the current feature flag with a rollback p…
No new filter types, keep existing dashboard URLs working, and deploy behind the current feature flag with a rollback path.
Tasks4/8 done
- Done
Reproduce the customer workflow
Watch the saved-filter workaround from dashboard load through the next morning.
- Done
Write the acceptance examples
Cover saving, renaming, applying, and deleting a private filter plus a changed underlying field.
- Done
Design the smallest data contract
Persist owner, name, versioned filter payload, and timestamps; exclude sharing.
- Done
Add ownership and RLS tests
Prove users can manage only their own saved filters and cannot infer another user’s names.
- In Progress
Implement save and apply
Use the existing filter validator and keep the dashboard URL contract unchanged.
- To Do
Test keyboard and empty states
Verify focus order, duplicate names, no saved filters, and a filter whose field was removed.
- To Do
Release behind the feature flag
Deploy, inspect errors and latency, then enable the flag for the requesting customers.
- To Do
Close the loop with customers
Ask each requester to apply a saved filter unaided and record the next missing piece.