Clicking elements when editing dashboards shouldn't be considered a change
RespondidaFeature Request Summary
When opening a dashboard to edit, Explore sometimes considersclicking on elementsa modification. The platform should track real changes, and ignore clicks on items.
Description/Use Case
Apart from still missing anaudit log(alsosee here) or track changes/version control features (like GoodData had), Explore has a "behavior" which can be confusing, especially when multiple editors are responsible for maintaining dashboards and queries.
Quite often, if we edit a dashboard, clicking an element seems to be considered achange,and Explore then shows the"This dashboard has unshared changes. Publish these changes to make them visible"notification on the bottom of the screen.
Example
管理员需要确认widge背后的东西t or query, so they'll edit the dashboard, click the element and review. No changes are made, the admin got his answer so they close the tab.
Moments later, an admin who's responsible for Explore maintenance goes to edit that dashboard, and sees that there are unpublished changes...
Business impact of limitation or missing feature
Continuing the above example: what changes? Who modified the dashboard? Everything looks the same.
Consequently, that admin will probably ask the team if anyone modified anything, which can be conclusive or not. And/or cross their fingers, hope that nothing critical was modified and republish the dashboard.
Additional food for thought: even if we were to edit a dashboard, click a query and edit that same query (opened via the dashboard) and save (going back to the dashboard)... Should Explore identify this as a dashboard change? Probably not (?) because it was the query that changed.
In the end, there is time consumed unnecessarily(besides being slightly stressful for admins!).Moving an element, even if 1px for example, is a change. But just clicking on it shouldn't be.
-
HiPedro Rodrigues,
thank you for spending the time to share your experience with Explore.
Clicking on an element shouldn't be considered a change to be published.
This behavior has been fixed on the new dashboard builder. The new dashboard builder is currently in beta and it is already available to all Enterprise customers. You can learn more about ithere.
As for the version control, this is something we will start looking into in 2023. While we can't share an ETA yet, this will be available on the new dashboard builder only.
Hereyou can find an exhaustive list of what we plan to roll out in the new builder.
Thanks again for your feedback.
Walter -
HiWalter Bellante, thanks for taking the time to share this update. Good news!
-
Walter BellanteIt looks like the EAP only applies to Live Dashboards, not to any others. Is there any plans to make this available for all Dashboards?
-
HelloCJ Johnson,
thanks for your interest.
Sure, in the next 2 weeks historical data, time and data filters will be available on the new dashboard builder.Make sure tofollow this articleto be informed once they are available.
Your feedback is welcome. -
HiCJ Johnson,
I just wanted to share that historical data, time and data filters are now available in the new dashboard builder.
You can learn more on how to use ithere.Feel free to give it a try and share your thoughts.
Thanks,
Walter -
HiWalter Bellante, thanks, but I'm not on a plan that gives me access, since the new dashboard builder is only available to Enterprise Suite plans. Are there any plans to make this available to the rest of the plans?
-
Additionally, this is marked as "Answered", but it's a request for a feature that is not available on the platform yet. Could it not be marked as "Answered"? It makes it seem like this is possible when it is not.
Iniciar sesiónpara dejar un comentario.
7 Comentarios