GA Input Controls

[nreese]

Input Controls in Kibana are currently in a experimental/beta phase. This does not mean, that there are any intentions of removing them again. Our current plan for Input Controls is to support them in the future, continue development around them and making them GA.

What are the steps we want to do before GA'ing Input Controls:

• Have a look at the open bugs and work them down. Important bugs:
  • Fix saved object references (Error importing Control type visualization #16634)
• Provide more documentation
• In context of the Dashboard refactoring we want to move over Input Controls (and Markdown) into widgets directly on the dashboard. Since that will bring some significant changes to the UI and experience around Input Controls, we want to make this move before GA'ing.

Updated by @timroes on January 28th, 2020

[thomasneirynck]

We'd also want to double check documentation-task, if there's enough!

[rayafratkina]

Do we need to find the solution to the sampling problem described in #47453 ?

[AlonaNadler]

High priority:

• Filtering in Control Controls Visualization Custom filtering #36744
• Case insensitive Make controls drop down case-insensitive #58517 friction point
• Default values in control Allow specifying of default values in Input Controls #56416

Missing :

• Support scripting fields

Need more thoughts:

• Input control should not filter all dashboard Use two controls in the same dashboard? #56672 Grafana allows that
• Fields and values Input Controls: Fields + Values #36595

Design:

• Reduce size when on dashboard Controls Visualization reduced size #43314

Main problem to solve:

• Improve input discoverability - users love input control, users have a hard time finding it (control name is not obvious, its current location in the chart types). Input control should be part of a dashboard setting
• Allowing users more control on the values in the input control - selecting specific values, filtering on specific values.
• Show end users only relevant values in the drop-down- currently only parent-child relationship and once applied users must start with the parent.

@ThomThomson @majagrubic @timroes @rayafratkina

[Heenawter]

Closing - the old input controls have been deprecated and are in the process of being removed entirely (once full parity is reached) in favour of the new input controls, which are already GAed.