Skip to main content
Inspiring
February 5, 2023
Open for Voting

Revert or discard changes in Team Projects

  • February 5, 2023
  • 18 replies
  • 2767 views

When using Team Projects, there is currently no way to revert or discard your own changes. If a user makes some mistakes, changes their mind, or doesn't want to "commit" unnecessary changes to the cloud, they don't have an option to reset to the last shared version.

 

This makes the feature effectively unusable, the user would have to push their changes regardless of whether they are desired or not. What if the changes are project-breaking? There is also no way to view the changes made and/or see a comparison to determine what changes were made.  (It would be great to see two timelines top/bottom and somehow highlight any sections of the timeline that changed)

 

At a minium, we need a "discard" or "ignore" changes because several times I have opened a team project, looked at a timeline, and accidentally "locked" the timeline.

18 replies

Known Participant
June 5, 2024

Any news from Adobe ? Does anybody from adobe team aknowledged this ? 
It seams like an unfinished product, we need "discard" asap

Participant
March 19, 2024

Just had the same problem and dug around a bit. One way to get back to a past version is to browse your Auto-Saves to just after your last sync update and then Right Click > Make Auto-Save the Latest

Closest I got to retrieving the last published version.

TRP-ScottAuthor
Inspiring
January 3, 2024

Sadly this is another example of a major company (Adobe) that does not need to care about its customes; or our wants or desires.  This was originally posted by myself nearly a year ago.  Despite multiple conversations with Adobe, including at NAB, absolutely NOTHING has been done to resolve this issue.

We switched to Davinci and I would suggest all others do the same.  
Until this hurts them in their wallet, nothing will change (and even then it probably wont b/c company's like Adobe simply no longer care about having happy customers or putting out a good product, as long as they can show a profit for their stockholders)

Participant
January 3, 2024

It has been some time since I used it (since my last post back in March 23 :), so things might have changed. If not, I think your out of luck buddy. I think you still are not able to NOT publish anything unfortunately.

Participant
December 29, 2023

HOW TO UNDO CHANGES? HOW TO NO PUBLISH CHANGES THAR YOU DO NOT WANT?

TRP-ScottAuthor
Inspiring
May 11, 2023

Any update - we DESPERATLY need this feature!!

 

I just had a sequence that Adobe thinks I 'edited' (because I muted one of the tracks), now it is not only locked, but there is no way to "undo" this "edit".  The problem is there is no way for me to be "100%" sure I didn't make any changes that would break it but now that sequence is locked for everyone else.

 

We need you to fix these things ASAP:
-Allow us to publish only specific assets

-Allow us to "revert" a single asset or an entire set of changes

-Allow us to make "non vital" changes to a track even when locked (i.e. mute/solo a track or hide a video track)

 

-Bigger feature: but it would be great if there as an easy way to compare changes (i.e. show me two sequences and highlight what changed)

Participant
March 23, 2023

I just realized this and it is absolutely crazy to me! The Publish window is literally only to add comments. And as you are not able to select anything in this window, you can't even choose what to publish and what not. This means, if you made anything you don't want to publish, but somethings you do want, you are basically screwed (or at least have to just accept the wrong changes into your publish project).

I totally agree with you that this makes the feature completly usuable and useless.

Participating Frequently
February 27, 2023

Yes! Just encountered this issue for the first time. An astoundingly bad UX decision not to have a "discard changes" option. This is an absolute necessity for any version control system. I actually really appreciate the team project system otherwise, but I totally agree with the OP that this is a very serious issue that merits dev time.