OpenOffice.org Issue Helper
A tool to help you submit a OpenOffice.org issue report in 5 core
steps.
How does this form help you submit an OpenOffice.org issue report?
Did you find something that does not work in OpenOffice.org?
Do you have a great new suggestion for a feature or enhancement to
OpenOffice.org?
Filing an issue is the first step to letting the OpenOffice.org QA team and developers know about your ideas and experiences.
The OpenOffice.org QA team and developers must be able to reproduce the problem and have enough information to analyze why the problem is occurring. This form helps you provide information that is needed by OpenOffice.org QA team and developers. They need this information to understand and reproduce the issue. Being able to understand and reproduce issues is the first step towards getting the issue resolved.
Please do not report bugs in other places. This includes the mailing lists, news groups, and IRC channels.
OpenOffice.org QA team and developers only work on issues filed in our issues database.
- Register as an OpenOffice.org user.
Create an IssueTracker account if you do not already have one.
After you receive your password, log in to the OpenOffice.org Website.
- Find out if OpenOffice.org knows about your issue.
We receive thousands of issues from our enthusiastic users. There is a chance that we may know about your issue already.
If you do a quick check to see if your issue has already been reported, you help save the OpenOffice.orgQA team and developers time and effort by avoiding a repeat issue (or as we call them, "duplicates" ). The OpenOffice.org QA team and developers review all issues posted by users, so repeat issues creates extra work for them.
You can check the list of duplicated issues.
If you do not find your issue here, then search IssueTracker here:
Enter two or three of the main words related to your bug. Try to keep them as generic as possible. For example: crash print or copy paste.
Look through the search results. If you do not get any results, check for misspellings in your search words or try other search words.
- If you find an issue that looks the same as yours, you can add comments to that issue, but please do not open a new issue.
- If you find bugs similar to yours, read them. Remember the component they were listed under; you will need to know the component later.
- Answer a few questions in 5 main areas.
The following are some questions for you to answer to help fill in your issue report to us:
- Submit your bug to IssueTracker.