+1. This would be extremely useful when we're working with less experience Git users who may or may not understand the commands they are submitting. Having some way of seeing exactly who did exactly what to our repo would be very handy in educating devs on better Git behavior.
As part of a security team overseeing various tools and services, the lack of this audit logging is making me seriously question future usage of BitBucket. This should have been added a long time ago...
@Jeremy Phillips i couldn't agree more. I'm being asked by compliance and senior management to lock down source code to protect IP... which obviously makes it very difficult for devs (especially remote devs) to work... having this level of functionality would prove to be be priceless in the event of a rouge dev pulling repo's on to machines they shouldn't be!!
as the administrator of the organization, This feature is required for auditing and compliance, ensuring that there is visibility into areas where source/IP is pulled, from what IP source code is cloned username and IP address and network. from which IP complete actions are performed.
How a basic clone log like this can be missing?
This is a required security feature (with IP address) to be able to find suspicious activity!
As manager I need a better way to see the read activity on the code, (not only the writing access!)
+1. It would be great to have this facility. Tracking everything is very important for any developer as well as an organization. This applies even for Bitbucket. Hoping to see this made available soon, with back dated tracker too.