That makes it sound like it was primarily the fault of the developer who created the bug - things like this indicate an inadequate process or culture not simply a mistake at the developer level.

Edit: Does Dropbox have any testers or is all testing based on automated tests created by the development team?

I expect it wasn't obvious at all. I think that sharing the details with the community might help prevent others from making the same mistake.