For us at least, any changes to an asset should be recorded into the asset activity history page. An example of this is that if a location for an asset is changed, it is never recorded into the history which obviously means that no agent would know the location had changed, or when it was changed unless a separate record for this was kept. 

This applies for ALL details that are changed such as serial number, asset tag, assigned date, file uploads, etc.

This would be very helpful. Conversely, if we could track a requesters asset history (with date periods of assignment) that would remove our need to keep a separate in-house solution for tracking who has had which phones/laptop/etc historically.

Great. It's good to see that Freshservice actually take feedback constructively, and where possible use it to improve their product. Credit where credit is due.

I also agree with Richard about Requester 'Activity', not just for assets themselves.

+1 on an audit log for the assets

This is crucial.

Being able to pull audit log on who updated the inventory date is necessary to use it for internal audit.

Example segregation of duty (not a feature by suggesting a usage)

1. Asset user - should prove the possession of asset by barcode scan -> This needs to be recorded in some new field like "Last Verified By" or something.
   
2. Asset Manager - defines assets, but should not update the "Last Audit Date" field himself/herself. Assign assets to users, and provide the asset audit log to auditor.
   
3. Internal Auditor - Receives asset audit log from asset manager, and shall be content by seeing that asset list is maintained by Asset Manager, but assets are verified by other personnel.
   
4. System - Should be robust enough to make the auditor believe that it is difficult to temper with the asset verification audit log.