FEATURE REQUEST: Add KQL filter on dropdown selection tool

[jrykowski-huron]

For current feature for visualizations to show a dropdown selection tool to easily add filter for dashboard, there’s need to only include values in dropdown that meet certain conditions. Right now you can specify index pattern, field, and options for whether to Multiselect and make Dynamic Options (update options in response to user input).

Need an "Advanced" option that allows for specifying a KQL search filter for the Field values

Use Case – for mssql Performance dashboard, only want to have hostnames in dropdown filter if they’ve got event.dataset containing “mssql.performance”.

[hendry-lim]

I believe the control viz, will be replaced by this #115991

[elasticmachine]

Pinging @elastic/kibana-vis-editors @elastic/kibana-vis-editors-external (Team:VisEditors)

[elasticmachine]

Pinging @elastic/kibana-presentation (Team:Presentation)

[ThomThomson]

This is a feature we can add to our roadmap for the new version of Controls!

[jrykowski-huron]

I believe the control viz, will be replaced by this #115991

Reviewing that it didn't seem to clearly include feature to dynamically filter the initial dropdown list based on KQL. Hopefully that'll be a thing with the new. Also that seems for 8.x? It'd be quite awhile before our organization would endeavor to upgrade to next Major release (a Minor 7.x release however... is more likely to occur).

[ThomThomson]

Hey @jrykowski-huron. The earlier linked PR was part of Phase I of the controls project, which is now complete. Phase one did not include the ability to write queries to narrow down the options on individual controls. Work is beginning on Phase II, and I have linked this issue there so we don't lose track of it.

The new controls are targeted for 8.x, and we aren't planning on adding any major new features to the old controls in Visualize. They were always marked experimental, while the new controls will be made Generally Available.

[ThomThomson]

For a fairly elegant workaround to this problem, see this comment. This should work correctly for both the older controls and the new controls project.

[ThomThomson]

Closing this in favour of the more general #140112