What is the proposed idea/solution?
On Interfaces, I would love for a user to be able to hover over an element and see the set of conditions/filters that are acting on the element.
How does is solve the user problems?
I often create dashboards that summarize data for my colleagues. My colleagues are not comfortable going into edit mode to see how an element was configured. Nonetheless, they may be interested in understanding what data a number element, for example, is drawing from. This would allow them to learn that without having to enter edit mode.
How was this validated?
Haven't validated it at scale, but I see this as a hurdle for my team regularly. The person who constructed the interface dashboard is the only one who really understands what the various elements mean
Who is the target audience?
Users of interfaces
...
