Submit a new bug
Summarize bugs in a report
Actions 1 and 3 do not require a Bugzilla Login, these can be executed either anonymously or from a
logged-in state.
Submitting a bug, however, requires a Bugzilla Login. This login is the email address where you would
like to receive updates on your reported bugs. The password will be saved server-side as well as client-side
(if you choose to allow saving cookies from this website), it is advised to use a nontrusted password for this
purpose. To create a bugzilla login, choose "Open a New Bugzilla Account" just under the Login: entry
area.
Standard Bug Reporting Procedure
Generally, the following actions are carried out when wanting to report a bug (this assumes a login has
been previously created):
• Search the existing bugs and determine if your issue has already been reported by someone else.
• If YES, call up the existing bug, and, after perusing the current state of known information and/or its
status, determine if you possess any new information that would be helpful if added.
• If YES, add all new information to the 'Additional Comments' section (or new attachments, or
whatever is possible) and Commit the change. You may also add yourself (and
any other known bugzilla user) to the CC: list to receive all updates to this bug in
the future.
• If NO, then nothing further is to be done: the bug is reported and known --> EXIT SYSTEM.
• If NO --> Proceed to Step 2.
• Enter a new bug report
• Please provide all relevant information when submitting a bug report. The more information that is
provided, the more complete the picture will be describing the various aspects of the state
of things at the time the bug or issue exhibits itself. Thus, the more likely it is that the
developer will be able to recreate the problem. This is the most fundamental aspect of
bug-solving: if the developer cannot recreate the problem, it cannot be solved.
• Once satisfied that all fields have been properly set and the description is as complete and accurate as
possible, select 'Commit'. This will generate an email to be sent to the developer assigned
to fix the bug.
• On the next-displayed screen you will be given the opportunity to add yourself to the CC list of email
addresses to receive updates on this bug in the future, if you so choose.
Your bug has been submitted, and if you have chosen to do so, all future updates to the bug will generate
an email to you detailing the update. If at any time you wish to be removed from receiving updates for a
given bug, simply call up the bug and remove yourself from the CC: list of emails receiving updates.
Products
Currently, there are two products for which bugs can be reported:
• PQL II
• PQLX
PQL II is a separate entity from PQLX. More specifically, if the bug exhibits itself within the Trace
Viewer portion of PQLX, then the bug should be reported under product=PQLX and component=PQL.
Bugs should be reported under product=PQL II only when executing PQL II itself, as 'pql', not 'pqlx'.
Other Information
By default, no email is sent to the reporting user when reporting a bug (all subsequent bug events do
generate emails). If you would like to receive an email of the bug when you report it, the following
instructions may help:
Once logged in, at the bottom of the page follow the hyperlink Prefs under the Edit: list of options.
Under the Tab Email Preferences, you will find all sorts of options pertaining to when you will receive