Revert feature is great, but lacking important things:

• current revert also delete new pictures
• current revert is reverting all the modifications
• revert does not send feedback to the user whose contributions have been reverted

Revert evolution

Here is how it could work:

• the user requests a product's page (for reading or editing)
• the system displays the page, listing each past modification in summary and offering the possibility of returning to a previous version [already done]
• the user selects a previous version and asks for it to be restored [already done]
• the system displays the details of modifications made to the previous version [new]
  • [alternative] the system displays the details of the changes made to the previous version, with the option of selecting which changes to revert
  • [option] the system also offer the possibility to write something to the user whose modifications are concerned by the revert (with moderators in copy)
• user validates changes to previous version
• the system saves the changes, keeping the images [new], indicating that this is a restore based on version XX
  • [option] if the "reverter" has asked for it, the system sends the email to the user whose modifications are concerned by the revert (from no-reply@openfoodfacts.org?), with moderators in copy

Revert monitoring

Revert should be easily auditable: what? how many? who?
A facet and an API route could be interesting to monitor reverts. Everyone should be able to use it. The messages should stay private but should be able to be seen by moderators.

Implementation

I have no idea on how to do this and how costly it can be. Maybe be we can do this step by step.

See also

• Add button to revert whole product to previous revision #1405
• feat: Revert product to a previous revision (API + upcoming website integration for moderators) #9800