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
Add manage Visualization in folder #13668
Comments
+1 |
thx for the feature request @nasirus. I can see how this would be valuable. You seem to want the ability to organize your visualizations in folders. As a work-around, right now, you could add some description to your visualization and search on that. Current users often now use structured values in these description fields to make searching easier. For example: "groupFoo - line chart for foo", "groupFoo - histogram for foo", "groupBar - line chart for bar" |
+1 |
any news to this topic ? |
Any updates? Customers are asking again. |
another year is over. This feature is still highly needed. Any updates ? |
I'll add my reasons for proposed prioritization from the dup issue I recently filed; Let's use the telemetry cluster as an example. This instance has a large number of custom visualizations intermixed with the growing number of OOB visualizations. These are displayed in a list format at up to 50 per page which results in a paged list of approximately 450 visualizations. If these could be grouped into folders, which could be expanded and contracted, they could be organized by topic or commonalities for the benefit of these user personas:
|
does tagging help support this use case? we have also modified dashboards so when you add a visualization it's "by value" (aka local to the dashboard and not in the library). |
still needed. like i said already 1 year ago: |
When we have many Visualization (More then 100) in production environnement, it becomes hard to manage it , so i suggest to add a feature to manage Visualization in folder something like in SSRS (Sql server reporting services) :
The text was updated successfully, but these errors were encountered: