Description of the problem including expected versus actual behavior:
:lady_beetle: Problem description
When clicking on a value in the histogram it automatically applies both a time filter and value filter:
Expected Behavior:
1. Instead of automatically applying both filters the app should show a popover asking which values to filter for
See behaviour in Discover:
2. Time fields should be applied as a time filter instead of a filter in the filter bar
Should have updated time range picker instead of adding a filter:
:female_detective: Possible approaches
The logic that defined this behaviour is inherited from the Lens embeddable / Unified Search (specifically part of the convoluted set of UI action interactions I outlined earlier in the thread), which puts us in a similar situation as you in that we don’t have control over it or which services it uses (it always uses the global filter manager).
figure out a way to have UI actions use scoped services (I’m guessing this would be hard but I don’t have a lot of experience here)
extract createFilterAction into a reusable function and consume it from the Unified Histogram customization using scoped services (probably the easier approach and still addresses the code duplication concern, although it sidesteps the UI actions framework entirely)
Follow up to https://github.com/elastic/kibana/issues/175323
Description of the problem including expected versus actual behavior:
:lady_beetle: Problem description
When clicking on a value in the histogram it automatically applies both a time filter and value filter:
Expected Behavior:
1. Instead of automatically applying both filters the app should show a popover asking which values to filter for
See behaviour in Discover:
2. Time fields should be applied as a time filter instead of a filter in the filter bar
Should have updated time range picker instead of adding a filter:
:female_detective: Possible approaches