Bug Guidelines
From Fortis
We genuinely appreciate the effort you have gone through to report any feedback or problems to us. All of your work will help us open our product up to a wider market.
The goal of writing a bug report is to help development reproduce your problem on their machines where they have the tools to diagnose and fix the problem. Here are some tips to writing effective bug reports:
Contents |
Search
- Search... someone else may have already reported the bug.
If you find it... Add a comment to:
- Provide new information or test files,
- Let us know the bug is important to you,
- Request to be added to the e-mail notifications for that bug.
Do not create a new ticket, just add comments to the existing ticket.
Describe & Attach
- Include the following sections in your bug report:
- "What you saw"
- "Steps to reproduce", and
- "What you expected to see"
Help us reproduce the problem... The information must be detailed enough to guide anyone to cause the same problem.
- Never assume we automatically know what you are talking about or what keys, mouse clicks, or files you used.
- Attach files that demonstrate the problem.
- Attach a screenshot as a .jpg or .png file. ( Important: Never embed your images inside a word document.)
Be Careful
- Review all the fields you are filling out.
- Sometimes the defaults are not correct. For example the default "component" to report your bug on is "auto update." ... Did you really want your ticket to be filed as a problem in the auto update system?
- Some fields such as "priority" should always be left as "not determined" when creating a new ticket.
- Other fields like "severity" have specific meanings, and if you fill this field out, you should first read the Bug Rubric
Follow Up
- Leave follow up comments. Don't let the conversation die.
- Reply to our questions promptly.
- Sometimes development will ask questions or request information in a comment. You will be notified by e-mail when this happens. Please return to the trac website and respond to the questions.
- Did development neglect your problem? Post a follow-up comment to "bump" the problem.
Be Brief
- Maintain a professional atmosphere in the bug reports.
- A concise report speeds up our work. A message may be read dozens of times before the bug is fixed.
- Conversational niceties such as saying hello are not necessary.
- Your login name is automatically recorded. There is no need to sign your message.