-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[8.0 Research] Filter Improvements and Alignment #88709
Comments
Pinging @elastic/kibana-presentation (Team:Presentation) |
Here's my dump of thoughts on Filtering as it exists currently in Canvas, and exploring ditching Canvas style Filters for bringing in the Filter Bar that is already familiar: Filtering Alignment Filtering in Canvas is unique from other applications in Kibana as it does not have the typical Filter Bar that users are accustomed to from Dashboard, etc. Instead, Canvas relies on elements which create filters. So instead of a filter bar with a KQL search and a timepicker, Canvas could have multiple drop down menus to filter on specific fields, as well as multiple time pickers to filter on multiple time fields. Users can also pick and choose which filters get applied to which visualization in a Canvas Workpad (via filter groups). This gives a lot of flexibility with how your elements in a workpad can be filtered, as every filter does not have to be applied. (Versus a KQL filter in a dashboard is applied to every panel) Current difficulties with Canvas filters is that it is very easy to get confused by which filters are being applied to which elements. We have an open issue with design to make it clearer how an individual element is being filtered #50984 So, what could we do to bring filters into alignment. I'm going to explore the idea of ditching the way filters are currently done in Canvas and bringing in the filter bar which is already familiar to everyone.
This would be a breaking Canvas change as we would have elements that no longer work and would need to be removed from workpads. Filter values are currently saved on those elements in the workpad, so they would likely have to move to the root of the workpad and interacting with the filter bar would mess with that, etc. I know there has also been some ideas of making dashboards be expression based, and if that were the case, then bringing the filter bar => filter group idea and function would be simple to bring across. I don't think this would cause any breaking changes for Dashboards as they are already using Filter Bar, so it would likely be a non-breaking change if we were to introduce the grouping concept. |
Closing because this no longer fits on our current roadmap 👍 |
Summary of Exploration or Proposed Change
Findings
The text was updated successfully, but these errors were encountered: