Project Bugzilla Update Planned to Version 3.4

The bugtracking tool used by the openSUSE project is the Novell bugzilla and this system will be updated to a new upstream version (version 3.4) together with some changes requested by openSUSE community and Novell employees.

The date for this upgrade is Saturday November 14 at 9am mountain time (that is 16:00 UTC). Both Bugzilla and Testopia will be down for several hours on that day.

New Features

There is a long list of enhancements in Bugzilla 3.4 , the user visible ones include:

• Simple Bug Filing

• Email Addresses Hidden From Logged-Out Users

• Shorter Search URLs

• Dates and Times Displayed In User’s Time Zone

• “See Also” Field

• Re-order Columns in Search Results

• Search Descriptions

• Other Enhancements and Changes

Additionally the following visible changes have been implemented:

Severity = Blocker

Of particular note is the change related to Severity=Blocker. We have introduced a new defect attribute named Blocker. This attribute can be set to Yes or No. To indicate that a defect blocks testing or development activities, set this attribute to Yes. The Blocker attribute can be shown in search lists, and you can query for defects based on this attribute.

The Severity attribute of existing defects will not be changed. If the severity of an existing defect is Blocker, it will remain Blocker. You can continue to search for defects with Severity=Blocker. You will no longer be able to set Severity=Blocker on any defect.

Report Another One (for This Product)

This was reported by an openSUSE tester against openSUSE and is a feature available in the KDE bugzilla as well.  It allows you after filing a bug report to file another bug report for the same product with the settings of the just filed bugreport reused.

Copy to New Records the Copy in the Old Bug

Copy to New is used to create new bugs for other versions of the product to make sure the a Fix gets put into multiple code bases. The New bug automatically gets the original Bug added as a Dependency, but if you are looking at the original bug, you cannot tell the other bug was created from this bug, and what that bug is.

It will now be possible to see what bug a bug was cloned from as well as any bugs that were clones of that bug.

Testopia

Additionally, the Testopia test plan tool will go from version 2.2 to 2.3. The list of fixes and enhancements for Testopia is available in the Mozilla bugzilla.