Autosave Dashboards

[timroes]

It would be great to have an autosave dashboard feature. If this is switched on (perhaps on a per dashboard basis in the new options panel) after the dashboard got saved once manually (and have a name) every change to the dashboard (adding/moving/scaling vis/searches) will be automatically saved.

I've often seen people saving their dashboards once and then forgetting to save after each change. Especially since the changes are temporarily stored in the URL so you don't notify immediately that you your changes are not persisted right now.

To prevent accidentally modifying dashboards, a "lock dashboard" setting would be a nice addition to this feature.

[gwired2015]

+1

[stacey-gammon]

Removing triage_needed label. I think it'd be cool to have, but can't fit on a road map any time soon. Would probably require undo/redo functionality as a pre-requisite and that would be a large feature. There was also debate, if I recall correctly, awhile ago when this feature was discussed previously, about whether we really would even want this functionality (or maybe the context was, we need RBAC first...). So this one stays on the back burner for the time being.

[flash1293]

I think the same thing would be equally useful for visualizations - maybe this feature can be abstracted for all saved objects?

Just thinking aloud at this point: Maybe it would be possible to implement this completely on the client-side with localstorage independent of undo/redo? One user is probably not really interested in the unsaved drafts of other users on the same instance.

See #26333

[timroes]

I am closing this in favor of #35812 where we're discussing aligned state and undo handling in general.