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.
Agreed! Any change should be captured in the activity list... We have this on our backlog already and we plan to revamp activity tracking across the product. More on this soon.
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)
I'd like to add my support here; having a history of which assets have been assigned at the requester level would be very valuable for us, for auditing purposes.