clearly details the problem: x happens at y place (and on which browser, hardware, OS)

provides accurate steps to reproduce the bug

install x,y,z modules, activate q settings (e.g. technical features)

go to e.g. Sales => Sales Orders

do this ... until the bug is produced

states what the correct behaviour should be if applicable

Also has a video/screenshot of the issue, preferably with the full path visible (menuitems, breadcrumb) to save time when the devs have to reproduce the issue (videos are best if there are many steps). This will make it more likely that your bug will be confirmed and assigned to a devs team, rather than tagged as incomplete.

Â· Any system failure - a complete stop in a workflow, a traceback error message, a button that does nothing.

Â· Any abnormal behavior of the system resulting from an issue with the code (if you happen to look that deep).

Â· Any security breach in the code of the software, any non-compliance with the law for accounting modules.

What is usually not considered a bug:

Â· Customer specific needs not being met. (It has to affect MOST people who use the system in a similar way.)

Â· Abnormal behavior or security breach due to defective installation or configuration

Â· Any usage of the software which would not comply with some industry standard.

Steps to take when you encounter a bug:

Do a web search for the error message, and for terms that might locate the problem and make sure there are no patches or bug reports covering what you have found.

Make sure you can replicate the bug on the latest branch of OpenERP, via http ://runbot.openerp.com - this rules out custom code or incorrect configuration settings.

If the bug is complicated to explain, make a video and upload to Youtube.

If the bug is directly related to a client, use the support alias with the client warranty number. If not specific to a client, use Launchpad to log it, and then send an email to the support alias that includes the LP link.

For Launchpad, click Report a Bug at the top of the following pages:

(Note the way bugs are reported with [7.0] or [trunk] in the Summary.)

Best bug report is the paid bug report :) After my OPW subscription my bug reports just got better. (both from my side and OpenERP SA side)
Without an OPW contract you can wait for too long. Since release cycle is too fast your bug report could even die untouched.

I also strongly recommend you to add screen recordings replicating your bug from runbot.openerp.com site.