[Discover] "Add Filter" treats field contents case insensitive, but does filter case sensitive #142064
Labels
bug
Fixes for quality problems that affect the customer experience
:DataDiscovery/fix-it-week
Feature:Filters
Feature:Unified search
Unified search related tasks
impact:medium
Addressing this issue will have a medium level of impact on the quality/strength of our product.
loe:small
Small Level of Effort
Team:DataDiscovery
Discover App Team (Document Explorer, Saved Search, Surrounding documents, Graph)
Projects
Kibana version: 8.4.1
Elasticsearch version: 8.4.1
Server OS version: Ubuntu 22.04 LTS
Browser version: Any
Browser OS version: Any
Original install method (e.g. download page, yum, from source, etc.): Any
Describe the bug:
When you have a field that contains the same information in different case notation (Example: host.name : Node01, node01, NODE01) between different indices (happens out of the box with different integrations), and you need to set a filter for that host.name, you need to add a filter like "field: host.name, operator: is one of" in Discovery. While picking the different case sensitive options, Kibana shows all 3 values in the list of host.name contents, but as soon as you add node01 as a value, Node01 and NODE01 disappears from the list and typing it says "node01 has already been added". The resulting filter, however, is case sensitive, so NODE01 and Node01 will not be shown in the results.
This is highly inconsistent.
Steps to reproduce:
Expected behavior:
If Filter UI value picker says "already picked" then the resulting filter should also be case insensitive
Screenshots (if relevant):
Errors in browser console (if relevant):
none
Provide logs and/or server output (if relevant):
not necessary
Any additional context:
This is an actual customer complaining.
The text was updated successfully, but these errors were encountered: