Remove ability to pin filters in embedded dashboards

[fakeh]

Hi all,

When a Dashboard is embedded users can still pin filters, which is meaningless in this context.

Dan.

[rkhapre]

this is useful, which is the power of kibana, discovering data and narrowing down the problem with filters, so useful in embedded dashboard as well

[marcinkubica]

-1

[fakeh]

Putting it another way then, what's the meaning of a pinned filter in an embedded dashboard?

[panthony]

I'm not really sure what do you mean by "embedded dashboards" as the only thing I have found on kibana is to embed a single visualization within an iframe (I may have missed something).

But in case we are embedding a single visualization I think we should have a way to disable filters.

Since the visualization is alone and out of context (not part of a dashboard) I see no value for the user to be able to filter on a specific category.

You just end up with the same chart and a single category (the one selected) and nothing else changed..

Another related issue, on histogram, is that if you filter on a category it will also apply a filter on the date range, and you have no way to go back. You must refresh the whole website you reload the iframe.

[fakeh]

the only thing I have found on kibana is to embed a single visualization within an iframe (I may have missed something)

@panthony You can also embed entire dashboards. Workflow is similar.

[spalger]

@fakeh I think you make a good point. The purpose of pinning a filter is so it will follow you from dashboard to discover and so on. On an embedded dashboard though it has no effect as the embedded mode aims to prevent you from leaving dashboard.

[rkhapre]

@rashidkpc
In Kibana 4.3.1, the pinfilters is removed from one Dashboard to another Dashboard.

In previous releases the pinfilter was working very well

This was the main theme of Kibana dashboard where we can pin the data in one Dashboard and go to other Dashboard to see a different visualization. This feature was very powerful, not sure why other folks in forums is opposing it.

I can explain 4-5 use cases where this is used in many organizations

Please let me know if there is any workaround on this?

[marcinkubica]

@rkhapre I can see pinning still works between dashboards. Ie, I can pin a filter and open different dashboard and pinned filter is retained.

What I find not useful is state of filter pinned is not being saved with the dashboard.

[stacey-gammon]

@spalger Re:

@fakeh I think you make a good point. The purpose of pinning a filter is so it will follow you from dashboard to discover and so on. On an embedded dashboard though it has no effect as the embedded mode aims to prevent you from leaving dashboard.

@robacj Brought up a good point on the PR that pinned state matters when moving from dashboard to another dashboard, which they are using in embedded mode, with the use of dashboard navigation in a markdown widget.

I'm tempted to just revert the PR since it was supposed to be low fruit and was not a high priority item. Since it turns out there were use cases I wasn't aware of, we will actually be removing functionality that some people may rely on.

cc @Bargs

[spalger]

Sounds like the best way to solve this is actually #9575

[stacey-gammon]

Agree with @spalger that this belongs as an option under #9575

Will close in favor of that, but link to this issue to keep track of this specific feature request.

[Kolano]

What's really needed is to alternately store pinned filters to allow them to work across separate dashboard iframes; not only when using navigation internal to a dashboard.

While we wait for #9575, injecting this style addresses hiding the broken pinning button...

/*Hide broken filter pinning button*/
button[data-test-subj="pinFilter"], button[data-test-subj="pinAllFilters"], button[data-test-subj="unpinAllFilters"]{
	display: none;
}