Audit trail for state and delegate changes #597
Description
Greetings,
I hope I am not creating a duplicate here, but I would like to ask if there is a plan for implementing logs for field changes connected with the user performing that action.
Why do we need this? Patches can easily "disappear" from the system when an incorrect state change is performed, like when a patch is declared completed it will disappear from the list of items where an action is required. Nobody will regularly look through other states on the off chance of finding an incorrectly modified item. Now at some point, these errors will be uncovered when the submitter of a patch complains and at that point, we want to know how that error could have happened. Was it an error from a bot handling patches? Was it an unintended or malicious change by a maintainer?
It would be optimal if a database table is filled with the field changes, containing the ID of the patch, the name of the user, the previous field value, and the new field value. Then it would be easy to find the offending action.
What do you think about this?
Regards,
Sebastian