My company has recently transitioned to using Revu sessions for projects. Previously we held these reviews with adobe, which also had the same problem:
Comments that have been marked completed, can be deleted at any time by the original user. In our workflow, if a comment has a status it indicates that changes have already been made based on that markup.
On occasion we get users that will change their mind on a markup and delete it, instead of editing or properly notifying the team that already made changes per their markup. Deleting the markup removes the record of changes already made, which makes undoing what was changed a game of I-Spy.
When this happens, we reach out to the user and explain the problem with deleting markups in this fashion. In Adobe we had to guess or remember who requested the change, so at least Revu does track when markups are deleted. It unfortunately does not track what was deleted. Reacting to the problem every time is not ideal as we work on a large team with users coming and going from the company, so the more air tight and preemptive fix would be the permission I have recommended below.
I suggest a permission category that allows full-control users to deny or allow users the ability to delete markups with a status. It would also be helpful to prevent users from editing markups with status too, as that can be an issue in a similar regard. At least in the case of editing the log does a good enough job of tracking those changes and their is still a comment on the document.
While this is a feature request, I am also open to any work around ideas anyone has.
(naturally I didn't pick the correct category for this post and I can't edit that. Can a moderator do that or do I just need to repost under the "Product Feedback" category?)
