Feature Request Summary
When opening a dashboard to edit, Explore sometimes considers clicking on elements a modification. The platform should track real changes, and ignore clicks on items.
Apart from still missing an audit log (also see 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 a change, and Explore then shows the "This dashboard has unshared changes. Publish these changes to make them visible" notification on the bottom of the screen.
An admin needs to confirm something behind a widget 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.
Vous devez vous connecter pour laisser un commentaire.