-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Unified search] Complex filter capabilities - Support ORs #127247
Comments
Pinging @elastic/kibana-app-services (Team:AppServicesSv) |
Pinging @elastic/kibana-visualizations @elastic/kibana-visualizations-external (Team:Visualizations) |
Hello! This seems to be completed, but when we can see it in Kibana release? |
It is available in 8.7! |
Thanks will try it. Din't know it's out. Very recently! :) |
Yes. It is up and running in 8.7. Thank you. What this feature lacks - it is ability to quickly add new filter from some Discover / Dashboard / Map by selected field value with OR relationship to already existing filters collection. That, in my humble opinion, makes this feature quite useless :( At least for my user cases. (Didn't meant to disappoint devs). |
@cyber-petushator something like that you mean? #148372 |
Thanks for reply! If you don't mind i'll try to give live example. Now what iam struggling to achieve is to give user ability to click on some field in tooltip which is uniquely describe entity (like IP address) to show all historical data about this entity. That in filter language should mean: |
Describe the feature:
We want to give the users the ability to create more complex filter expressions by supporting ORs.
Currently, the users are able to create one filter at the time and all the filters applied are related with AND. (filter1: A AND filter2: B etc). We would like to enhance our query builder in order to give the users the ability to create N-depth complexity filters related with AND/ORs.
The UI will look like this:
Tasks:
Step 1 (preparation):
Notes:
- nesting is limited by the passed parameter;
- user should be able to add/modify multiple filters with complex relationships;
- new component should support drag and drop experience;
- new component should be developed with the focus of what will become shared.
Step 2 (integration):
Notes
The text was updated successfully, but these errors were encountered: