Drilldowns do not take over values from Controls

[mpbraendle]

**Kibana version: 8.3.3

**Elasticsearch version: 8.3.3

**Browser version: Safari, Firefox

**Browser OS version: Mac OS, Windows

Describe the bug:

In the Kibana dashboards, I've replaced the Input Control Visualisations (that were outlined as deprecated) with the new controls.

However, a drilldown does not take over the values that have been set by a control, as this was the case before with the Input Control Visualizations. This is a bug.

Steps to reproduce:

1. Go to https://www.oamonitor.uzh.ch/en/faculties.html
2. Choose a value from the "Communities & Collections" dropdown menu, e.g. "04 Faculty of Medicine". Control applies to the current dashboard.
3. Then click on a visualisation (e.g. the Green piece of the pie chart), then choose either "Apply Filter to Current View" or "Go to Publishers and Journals".

==> the Dashboard forgets the previously chosen "04 Faculty of Medicine"

Expected behavior:

This is not the way it should behave. Controls should work like filters and add a filter to the filter bar, as before with the control visualisations.

[elasticmachine]

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

[ThomThomson]

@mpbraendle, thank you for raising this! We are currently in design phase of the next step of this project, which is to unify the Controls and the Filter bar into one system. Once this is completed, drilldowns will work correctly.

That said, we have considered adding a system to make the new controls work correctly with Drilldowns in the shorter term, and this may be prioritized. @teresaalvarezsoler FYI.

As a workaround, I would recommend that you continue to use the legacy Input Controls for the time being. They are deprecated, but they will continue to work, and will not be removed until long after the new Controls are entirely feature complete.

[mpbraendle]

@ThomThomson thank you for answering. I've reinserted the legacy Input Controls in the dashboards where necessary.

It's unfortunate that Kibana 8.3.3 displays a deprecated message and recommends to use the new Input Controls although they are not finished yet. I would have expected the full functionality in such a case. Changing forth and back all dashboards and adapting the webpages cost me a few hours of work.

On another note, the user-friendliness of the new Input Control's drop down menu should be improved. The Select... and search field should be combined into one field - now the user needs to click twice.

[ThomThomson]

Our apologies for wasting your time, the new Controls are a full architectural re-write to be more maintainable and unified so sometimes things can fall through the cracks where features interact. Drill downs are a great example of this.

In terms of the Options List requiring two clicks to search, that's a UX issue which should be an easy fix. We can't use the value area as the search box, but we can auto-focus on the search box when the popover opens, which also saves a click. I've created an issue to track that feature addition.

[jbyroads]

@ThomThomson Wanted to add this is impacting us pretty significantly as well. We did not use the legacy input controls because we had issues with them. We're undergoing a complete overhaul where we are leveraging the new controls, so reverting back to legacy input controls is not really an option.

That said, we have considered adding a system to make the new controls work correctly with Drilldowns in the shorter term, and this may be prioritized.

Is there another ticket created specifically for this shorter term solution that I can track?

[ThomThomson]

@jbyroads, I've just created this issue to outline the shorter term solution. We have also discussed this with product management today, and have decided to prioritize it! You can follow along there.

[jbyroads]

@ThomThomson - great news. Thank you sir!