Problem Statement
Dashboard widgets cannot reference each other. There is no way for one widget to consume the computed output of another widget on the same dashboard.
The use case is a drill-down scoring view for mobile performance:
[ Team A Score ] <- composite score, weighted
[ Screen X: TTI | FF | SL ] [ Screen Y: TTI | FF | SL ] <- per-screen tables
The bottom row is a set of table widgets showing per-screen metrics (time-to-initial-display, frozen frames, slow frames). The top widget should be a single composite score derived from those same values, each multiplied by a weight and summed.
Today there is no way to consume the values already computed by the lower widgets. The filters, fields, and formula all have to be re-declared inside the score widget. That means:
- The same filter/aggregate definitions are duplicated across every widget on the dashboard.
- Any change to a screen's filter has to be manually mirrored in the score widget, or the two silently diverge.
- The relationship between the score and its inputs is invisible to anyone reading the dashboard — there's nothing linking the composite to the widgets it's supposedly derived from.
This scales badly. A dashboard covering N screens across M teams requires the same definitions restated in every score widget, with no single source of truth.
Solution Brainstorm
No response
Product Area
Dashboards
Problem Statement
Dashboard widgets cannot reference each other. There is no way for one widget to consume the computed output of another widget on the same dashboard.
The use case is a drill-down scoring view for mobile performance:
[ Team A Score ] <- composite score, weighted
[ Screen X: TTI | FF | SL ] [ Screen Y: TTI | FF | SL ] <- per-screen tables
The bottom row is a set of table widgets showing per-screen metrics (time-to-initial-display, frozen frames, slow frames). The top widget should be a single composite score derived from those same values, each multiplied by a weight and summed.
Today there is no way to consume the values already computed by the lower widgets. The filters, fields, and formula all have to be re-declared inside the score widget. That means:
This scales badly. A dashboard covering N screens across M teams requires the same definitions restated in every score widget, with no single source of truth.
Solution Brainstorm
No response
Product Area
Dashboards