What problem are you trying to solve?

Focus on the what and why of the need you have, not the how you'd like it solved.

Filtering a dashboard consistently across every widget only works today if all underlying widgets are built on directly filterable fields. Widgets built on custom aggregation pipelines can't be controlled by the standard dashboard filter, so we end up needing separate, near-duplicate dashboards for different filter values (e.g., different time periods or segments).

What would you like to see happen?

Describe the desired outcome or enhancement.

Ability to define a dashboard-level input/parameter that end users fill in at runtime, which then applies consistently across all widgets on the dashboard — including those built on custom pipelines.

Why is this important to you or your team?

Explain how the request adds value or solves a business need.

It removes the need to build and maintain multiple near-duplicate dashboards just to change one filter value, and gives less technical users self-serve control over what slice of data they're viewing.

What steps, if any, are you taking today to manage this problem?

Building a separate dashboard per filter value/segment, or relying on drag-and-drop dashboard filters, which only work when every widget happens to already share the same filterable structure.