Bugzilla updated to 3.4.6

All Bugzilla instances have been updated to 3.4.6. You can read about all the changes here or just the differences below.

• When doing a search that involves “not equals” or “does not contain the string” or similar “negative” search types, the search description that appears at the top of the resulting bug list will indicate that the search was of that type. (Bug 474738)
• In Internet Explorer, users couldn’t easily mark a RESOLVED DUPLICATE bug as REOPENED, due to a JavaScript error. (Bug 546719)
• If you use a “bookmarkable template” to pre-fill forms on the bug-filing page, and you have custom fields that are only supposed to appear (or only supposed to have certain values) based on the values of other fields, those custom fields will now work properly. (Bug 538211)
• If you have a custom field that’s only supposed to appear when a bug’s resolution is FIXED, it will now behave properly on the bug-editing form when a user sets the bug’s status to RESOLVED. (Bug 520993)
• If you are logged-out and using request.cgi, the Requester and Requestee fields no longer respect the usermatching parameter–they always require full usernames. (Bug 533018)
• If you tried to do a search with too many terms (resulting in a URL that was longer than about 7000 characters), Apache would return a 500 error instead of your search results. (Bug 513989)
• Bugzilla would sometimes lose fields from your sort order when you added new fields to your sort order. (Bug 470214)
• The Atom format of search results would sometimes be missing the Reporter or Assignee field for some bugs. (Bug 537834)

No Hassle Open Source Project Management Hosting