Revert to last published state - "unpublished changes in editor"

11 Comments

  • Klaas Römer
    Comment actions Permalink

    Especially since the "undo" button doesn't seem to work properly on all changes, this feature would be highly appreciated.

    2
  • Efrat Barak Zadok
    Comment actions Permalink

    I second that! I run the automatic re-organizing and now I can't go back. 

    2
  • Kevin Vliet
    Comment actions Permalink

    +1. I re-organized my widgets without first cloning my tab and doing so completely wrecked my dashboard. Lots of time and effort required now to undo what was done. A simple undo or revert changes would be extremely beneficial to have in situations like this. 

    2
  • Stephen Belleau
    Comment actions Permalink

    I found this very frustrating as well. IMO this should be prioritized as a bug fix rather than a new feature request. Not being able to edit the current version of a dashboard can be pretty crippling if someone has been testing things.

    1
  • Robert Hoogendam
    Comment actions Permalink

    Agree to the above, I almost could not resolve the issue caused by undo function.

    Disregarding and/or reverting changes pending in the editor is needed.

    1
  • Katherine
    Comment actions Permalink

    This must be addressed ASAP. Lots of time and effort to undo changes. Copying dashboard doesn't work, as it keeps the unpublished dashboard changes.

     

    1
  • Bruno Cruz
    Comment actions Permalink

    I've also had to redo dashboards due to this issue and find it strange such wasn't envisioned or considered problematic before launching Explore. The undo feature doesn't fully work and, even if it did, doesn't seem like good UX to be undoing multiple changes just to get to the last published state.

    Without this, I think I'll just stick with Insights until it's absolutely necessary to switch or until Explore is ready for production.

    1
  • Terry Ehrhard
    Comment actions Permalink

    I would like to further show support for this need.  After using Explore for a while, although I appreciate the auto-saving aspects, the need to revert back to what is currently in production is sorely needed.  It is not productive or useful to have to make a copy each time you want to make changes and re-invite everyone who previously had access to the original report/dashboard just so you can revert back.  Frequently the need to experiment with a change to see how it will respond or intent to make a fix that might not be what is intended, but if a copy isn't made then you are basically screwed and you have to figure out how to undo what you just did.  This is poor functionality that needs versioning.  Think of any versioning system where you can select a version to revert back to.  That is what is needed....

    1
  • Matt Taylor
    Comment actions Permalink

    Vincent Dollet would this be possible? It seems like we are all experiencing the same pain point.

     

    0
  • Vincent Dollet
    Comment actions Permalink

    Thank you all for your feedback on this topic. We do intend to enable you to view recent changes & revert to an earlier version, however I do not yet have an ETA.

    Many thanks for your continued patience

    1
  • Chad Hanna
    Comment actions Permalink

    Agreed on this being something that is needed.  Having unpublished changes stuck in the editor makes it extremely difficult especially with the training being as limited as it is starting out.  If you want users to come up with innovative new views and train ourselves, we need the ability to edit without fear that we will make the dashboard not editable later without creating a clone.

    0

Please sign in to leave a comment.

Powered by Zendesk