A.This is not a defect, working as designed. The reason that the record is updated is that the time slicing job is updating data in the record based on the changes to the resources' availability calendar. The same thing will happen on tasks. This update is provided for security and compliance reasons to indicate that the data in the record has been modified.
The Audit Trail captures changes via a database trigger and logs the changed values in the CMN_AUDITS table. From this table, we display the before and after changes for a particular attribute under the "Audit" tab. This issue comes into play because we do not log a Studio datatype information in the CMN_AUDITS table. So, a database NUMBER, DATE, MONEY etc may differ with a Studio NUMBER, DATE, MONEY, PERCENT etc
Therefore, this is the reason why it is by design and so we must find out what the PM/user is doing specifically as that is the insight into why when reviewing the audit trail, to not assume the actual user did it. The audit trail merely tracks a change, and this does not infer the actual resource actually made the change directly.