- Filing Issues
- Issue Handling
- About Issue Tracker
- Why Use Issue Tracker?
- OpenOffice.org Issues
- OpenOffice.org Infrastructure Problems
Enter a new issue
If your issue has not been reported, then you need to submit a new issue. Read the guidelines for reporting issues page to learn how to report an issue/bug. See also A Quick Introduction to IssueTracker.
You can add attachments to issues. The limit is 10MB, but please keep any attachment small, as most people use 56K connections. Attaching a file to an issue is a two-step procedure and is not obvious. You must first submit the issue or locate the issue to which you wish to attach the file. Then, you can add the file as an attachment to that issue. There will be a link in the issue body that reads:
Create a new attachment (proposed patch, test case, etc.)
Submitting issues is only the first step. Depending of the type of an issue, it will pass several
stations during its life time. For instance, when a bug is submitted, usually the following happens:
Somebody from the QA team will have a look at it, to at least ensure that it's in a useful state (btw: if you follow the rules for issue submission, you can already help a lot in creating an useful issue). After this, somebody needs to fix the issue (usually an engineer, but possibly also somebody maintaining documentation). Finally, when the fix made it into the product, somebody needs to verify it - usually again an QA engineer.
OpenOffice.org uses a modified version of mozilla.org's BugZilla to track issues. Issue Tracker is integrated into CollabNet's SourceCast, upon which the OpenOffice.org website runs. This document was written for IssueZilla, Issue Tracker's predecessor. It is still relevant. However, an excellent account of the current Issue Tracker can be found in the Help.
If you are a registered user of OpenOffice.org, you can use Issue Tracker to browse existing issues, enter new issues, or modify the details of an existing issues. Please be aware that you'll need to enable cookies in your browser to use IssueTracker.
Why use Issue Tracker and not a mail list? Because it allows everyone to keep track of the many big and small tasks, requests, enhancements, whatever that circulate throughout an Open Source project. What is more, the issue tracker makes it easier to determine if any another user has had similar problems. And if the problem has been resolved, it can alert the relevant people to the solutions found. In short, by registering and then filing issues with Issue Tracker, you become a contributing member of OpenOffice.org.
Note: You can delete your SourceCast account and thereby disable your Issue Tracker account at any time. However, if you then decide to re-register using the same account information, you will not be able to file issues. This is because Issue Tracker accounts are never full deleted, only disabled. You thus have to initiate a new account.
Issue Tracker will notify you via email about changes made to issues you reported. Please do not reply to these messages but login the website and add your comments to the issue. If you don't want to receive these notification emails you may want to edit your Issue Tracker preferences and change the email settings.
You can report and query issues in the OpenOffice.org code/documentation/ui/definition. Issue Tracker currently reports and tracks the following issue-types: DEFECT, ENHANCEMENT, FEATURE, TASK and PATCH (we can, of course, add new issue types as necessary). For example, you could report a bug as DEFECT; Track ENHANCEMENT requests to existing features; discuss adding new FEATURES; track a TASK for others to do (delegating or requesting help). Furthermore Issue Tracker is also used to track PATCH submissions.
If you find an issue with some part of the OpenOffice.org infrastructure (not
the application), such as a problem with the site search engine, or a problem
with CVS, please use the component www.
$Revision: 1.12 $ $Date: 2007/02/23 10:49:16 $