-
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
Dashboard pages/tabs #15120
Comments
This looks great. Is it still being considered for development? |
Yes, this is still on our roadmap. Will probably not be worked on till version 7.x though, since that's when the new designs will make it easier to add this feature in. |
That's great news! Looking forward to seeing this in action. |
With the pages selection above the query and filter it feels like the UX would be that each page can have it's own query and filter. Is that the intent? I just want to get an idea of what the plan is for the pages. I personally would like to see both an individual query filter for each page option as well as a synced query and filter between pages option where they persist between pages. |
It does give that impression @JacobBrandt, since the pages navigation is above the filter bar int he mocks. I don't believe that was an intentional decision though (unique filters per page). I think it makes sense to have a global dashboard query/filter and then per page/tab filters/query. We'd just have to figure out the UI (sounds like this could be inline with your other issue - #16898 - if the dashboard level ones were not changeable in view mode). We'll have to think through this aspect more, once we can shift full focus to this feature. |
Linking to #12562 as this is somewhat related |
Any new on this feature? Tabbed dashboard navigation would allow us to build much more detailed dashboards containing subsets of information etc.. |
This will be a larger project, so closing this issue in favor of the more detailed meta issue #136680 |
Allow multiple pages or tabs on a dashboard.
Somewhat different than #12562 as that issue really only indicates playing through different dashboard, while this one would be a single dashboard with multiple pages that you could cycle through.
Similar ideas but different UX flows. Having dashboard pages may also help with a lot of performance complaints, since we could load visualizations from other pages behind the scenes, and the first page would load first.
The text was updated successfully, but these errors were encountered: