-
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
[Dashboard Usability] Expose all filter sources #152025
Comments
Pinging @elastic/kibana-presentation (Team:Presentation) |
As discussed in #137206 we expect to show filters applied to a panel in the Panel settings flyout for a simpler UI. Once we add filters to the Panel settings flyout, do we still need to include filters in the Inspect flyout? The Inspect flyout shows the request and response bodies from Elasticsearch which (in a way) already show the filters applied. |
Since we already added the filters to the Panel Settings flyout, should we close this issue? @cqliu1 ? |
@teresaalvarezsoler This is more for adding a more detailed view to the It's worth spending some time thinking through a redesign for our inspect panel UX overall and what information would be valuable to the user to see in view mode. @andreadelrio I'd love to hear your thoughts on how we could improve the |
I think it may be more valuable when we do this other issue #170395. Let's keep it open then. |
It might be sufficient to just add additional filter sources to our current panel settings filter view. Currently this section only shows filters saved as part of that individual panel. We should tackle this work along with #170395 simultaneously. |
I just wanted to mention here once we introduce this dashboard setting for ignoring irrelevant filters, we should also show which filters are ignored in this view. |
We should add a detailed view showing all the filters being applied to an individual panel, probably in the inspect view.
There are many sources for filtering/querying, and it would be valuable to create a centralized place for users to see all the filters applied to each panel and where they come from.
The text was updated successfully, but these errors were encountered: