One of the most important things a user of OOo can do it file an issue. Issues can serve several purposes. They are used for:
- Reporting defects in the program
- Requests for enhancement
- Feature requests
- Tasks
- Patches
The last two of this list won't concern most users. The first three is where every user can help. Any user without any programming experience or in depth knowledge of computers can file a defect, a request for enhancement (RFE), or a feature request. Filing an issue is a fairly simple task.
- You need to be a registered user on OpenOffice.org. If you aren't registered instructions to become registered can be found here.
- If you are already registered, proceed to OpenOffice.org. Click the My Pages link on the main page. If you are not logged in, the login screen will appear. After you log in, the following page will appear, although the content will vary by user.
- On the left hand side of the page there are five links. Click on the File issue link. You can also bookmark the following link http://qa.openoffice.org/issue_handling/pre_submission.html. The following page will appear:
- Before you file an issue you should check to make sure the issue hasn't been filed already. This saves times for you and for the people that evaluate issues. Also, if an issue has been filed and resolved it may answer your question without having to wait. To search for an issue use the Query page.
-
If your issue doesn't exist, you can now start to think about filing the issue. On the pre submission page you will see 5 things you should remember while filing an issue:
- One problem - one issue
This is probably the most important instruction. Limit each issue you file to one problem or suggestions. If you don't part of it may be resolved and the rest ignored. This isn't usually a problem when filing defects. This is more of a problem when file RFEs or feature requests. People will put two or more suggestions in one issue. This is difficult for developers to use, because each suggestion is a separate process for them.
- Provide a meaningful summary
Summary is key because people searching need to know what the issue is just by reading the summary.
- Provide step-by-step descriptions
Also very critical. If you file an error or defect, you need to tell exactly how someone else can make it happen. If the issue can't be re-produced, the developers and QA volunteers will assume it is your computer, not OOo.
- Provide sample documents, if possible
Screen shots are invaluable. A picture equals 1000 words and that is true here. I have even seen people attach videos to show what happens. However...
- Use Attachments reasonably
Don't go nuts with attachements. Try to use common sense
If you have considered these things, click the Go on - Submit the issue link.
-
The first challenge you will be presented with is a list of Components.
This can be daunting when you first see it. Read through the list to find the component you need. Some of the more common ones are in the following table.
| Description |
Component |
| Writer (Text Documents) |
Word Processor |
| Calc (Spreadsheet) |
Spreadsheet |
| Draw |
Drawing |
| Presentation (Slide Shows or PowerPoints) |
Presentation |
| Issues that are common to all parts of OOo. This is often where general RFEs or feature requests might go. |
Framework |
| Spellchecker |
Ligucomponent |
Click the component that most closely matches your issue.
-
On the Issue Submission page there are several fields you need to fill in. Fill in these fields and click submit before you try to vote for the issue or add attachments. This is the issue submission page:
The fields you need to fill out and a description of them are:
- Version (Required)
Pick the version you found the error in. For beta versions of OOo 2.0, you need to indicate the build of the beta. In this list the build is denoted by an "m" followed by the build number. To find your build number, in OOo select Help > About. If your version is 1.9.104, then your build is m104.
- Subcomponent(Required)
The list of subcomponents will change depending on the component you are reporting in. Try to pick the one you think matches your issue best.
- Platform
Generally this field shouldn't be changed.
- Priority
Don't change this field.
- OS
Select the OS that you are using. If the issue is confirmed on more than one OS, the QA team will change it.
- Issue type
Select your issue type here. The issue types are described at the top of this page.
- Summary
Fill out as succint a summary as possible. Use key words that others will find when they search, but also be descriptive of the issue.
- Description
This is where you can describe your issue. If it is a defect, make sure you give step-by-step instruction to reproduce the issue.
- Click submit.
Back to top. Ways to contribute. Contact the webmaster.
Last Edited 07 July 2005
