|
| Bug Writing Guidelines
Feel free to refer to the Bug Writing Guidelines that come with Bugzilla, or How to Ask Questions the Smart Way.
Basically, it all comes down to stating your problem clearly and courteously. Eager users that are both patient and polite will find that developers will make an extra effort to fix bugs and solve problems as soon as possible.
Don't forget to include the following:
- Specific steps for reproducing the bug - what you were trying to do right before the bug happened;
- How things went wrong - any error messages, or descriptions of the bug's behavior or appearance;
- Expected results - how you expected the application to behave, or how it has worked in other cases;
- Severity - if the bug is
- Criticial - preventing you from logging in or doing any editing,
- Major - causing data loss or making displayed content unreadable,
- Minor - preventing editing or completion of a specific item, or
- Enhancement - a request for a new feature or tool;
- Info about your environment - the browser version/type and operating system you are using. If your browser and OS are not in the list, please list them in the Description field.
After double-checking your information and descriptions, click 'Submit' to send your bug report. The development team will respond within a day; however, it may take longer to fix the reported bug or develop the requested enhancement.
Note: Access to Bugzilla is restricted to specific users. This form is intended for use by all other users. Bugs submitted here will be entered into Bugzilla by an authorized user.
|
|