Revert to previous version

Owner: Rebecka Hall 

What business value does this roadmap item create? / Which problem is this roadmap item trying to solve?

Revert to previous versions allows authors and editorial staff to restore a version where the content of the review is in a better state than the draft version. 

Revert can also be used to re-publish protocols where the draft of the full review is already in process (it's unclear how often this is done).

How can the value delivered be measured?

The feature is actively used.

Which assumptions are made in relation to the value?
It's clear to users that tagging versions often gives a more granular selection to revert to.  

What are the dependencies for fulfilling the business value?
The solution should be easy to adapt to when ReviewDB generates JATS instead of RM5 format.

There needs to be a way to view the content of a review version before reverting to it RMW-1158 - Getting issue details... STATUS . The review History needs to be accessible for all reviews:  RMW-1125 - Getting issue details... STATUS

What are the risks related to this roadmap item?

If the functionality to revert is removed in Archie you will loose the ability to revert to versions that are not in RevMan Web. When this feature is released all intervention reviews will be available in RevMan Web which means that all checked in versions after that are in RevMan Web. 

What is included in the scope of this solution?