Gilles has a great answer. Our procedure is below:
First consider what is usually considered a bug:
Â· 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.)
OpenERP Addons http ://bugs.launchpad.net/openobject-addons
OpenERP Server http ://bugs.launchpad.net/openobject-server
OpenERP Web http ://bugs.launchpad.net/openerp-web
Describe the bug in the following way:
Â· Steps to reproduce:
Â· The result observed:
Â· The result expected:
Â· The operating system and platform and browser being used:
Â· The OpenERP version and revision from runbot you tested on:
Â· Any additional information (screenshots, documented walkthrough, video, forum discussion, related bug, etc):
We have a few other steps to include the bug in our internal tracking system, but that's the process we use for all bug reports.
In our experience it makes everyone's life easier and makes the most efficient use of everyone's time - it cuts down on the time to understand the bug - which is the longest part!