Immutable filters on dashboards

[JacobBrandt]

Describe the feature:
A way to save a filter on a dashboard that cannot be removed. We want the focus to always be on whatever filters the dashboard creator applied and don't want the users to change them.

We currently have to do this by having multiple versions of our visualizations with different filters saved on them.

[stacey-gammon]

Sounds like part of #9575 might help - the ability to specify whether or not to allow filters to be edited in embedded mode. Would that work for you @JacobBrandt?

[JacobBrandt]

Didn't see that one. That's more like what I was asking for in #16766. Users could do everything in a previous version we had and now when we try to update the users get limited functionality which prevents our ability to update which really sucks.

For this feature we want the user to be able to do everything on the dashboard except change some fitlers we've locked. The use case is we want the focus to be on a particular filter (let's say a geo spatial one) or set of filters and don't want them going outside the parameters of that filter. They should however still be able to do everything else including adding additional filters, moving dashboards, ,etc.

Right now to accomplish this we have to create and save these filters on every visualization and add it to the dashboard. This means we are duplicating visualizations anytime we need to accomplish this use case. It's really time consuming. If instead we could keep a locked filter on a dashboard we wouldn't have to create so many duplicate visualizations.

[stacey-gammon]

Ah I see.

I'm currently fleshing out this feature: #16917, though sounds like you are more interested in filters, not index patterns.

It is a pretty interesting request, though requires some design thought, like how to set the locked filters and how to visually indicate they can't be removed. For example - should we keep them in the query bar/filter bar, or do we throw them into the options dialog so they can't be edited in view mode? The latter approach would hide them from the user, which perhaps is desirable.

[JacobBrandt]

That's also a cool feature. Yea, we need filter support instead of index patterns because typically all our dashboards are across multiple indexes. I'd be fine with either approach; hiding or indicated they are locked or maybe even hiding with some lock icon that upon hover explains how it's been locked to certain filters.