Internal guide to report a bug

This is the mail I sent to the internal mailing list in vizzuality some weeks ago when we started to prepare the next big release of CartoDB (probably it will be live when you read this post) with some guidelines to report bugs while manual testing is performed. I think it might be useful for you:

Hey,   The following days we will report lot of bugs (I hope not …) and there are some things we can do to improve the time they take to be resolved:

and the last one but not less important: