Repository navigation
fix(frontend): Potential Monthly Savings differs between Home and Opportunities for the same recommendations #180
Description
Where: Home vs Opportunities summary cards.
What happens: Home shows Potential Monthly Savings $210 – $326 while Opportunities shows $227 – $358, both for the same 47 recommendations.
Expected: the same KPI agrees across screens, or the scope difference (e.g. filtered vs all) is labeled explicitly.
Why it matters: same-named KPIs that disagree erode trust in the numbers.
Source: docs/ui-ux-review.md (2026-08 UX review) (finding 2.4)
Activity
IAmJSD commentedon Oct 24, 2026
Claiming: working on this
fix(frontend): label the Opportunities savings card when a filter is …
Merge remote-tracking branch 'origin/main' into ui/issue-180
test(frontend): expect the em dash placeholder on Home's failed-fetch…
Merge remote-tracking branch 'origin/main' into ui/issue-180
fix(frontend): make Home and Opportunities agree on Potential Savings (…
IAmJSD commentedon Oct 26, 2026
Closing as fixed on main. #1328 makes Home honor Enabled Providers through a shared filterByEnabledProviders helper, so Home and Opportunities show the same Potential Savings figure. When column filters narrow the Opportunities card, it now says 'Filtered: X of Y'. This meets both outcomes the issue accepts.
Left as a judgement call, not an acceptance criterion: Caveat only: the exact $210-326 vs $227-358 numbers from the review could not be reproduced. The Home per-service chart's Current/Committed layer still ignores Enabled Providers, which would need a backend change.
The fix PRs said Refs, so GitHub did not close this automatically. Checked against main on 2026-10-26 by IAmJSD's agent (IAmJSD is acting owner while the maintainers are away). Reopen if anything here is still wrong.