Edit Issue page redesign with actions bars, Collapse/Expand All button for all comments and etc.
New Bugzilla Homepage that presents:
Products statistics per target version
The list of new and open issues for the logged user
An Issue Type feature, for using Bugzilla as an Issue Tracker to track task, bugs, features and etc.
New Subtasks functionality - this option helps to split an issue to a number of smaller tasks that can be assigned to different components and users, thus providing a better picture of the progress on the issue. This new feature also allows each party that needs to be involved in resolving the issue to better understand what part of the process they are responsible for. Good example for use of this functionality is the Feature Management.
Additional features enabled by inclusion of Subtasks:
Issue of any entity type in Bugzilla can have subtasks (defined per entity type).
Issue of any entity type in Bugzilla can be a subtask (defined per entity type).
"final" list of subtasks can be defined for an entity; additional subtasks can be added in this case as well.
Validation of issue's subtasks on "Resolve" can be "turned on" for an entity – means that user can not change its status to "Resolved" as long as there are open subtasks for this issue.
Subtasks Report - a general report that shows issues with their subtasks and statuses, grouped by entity type of the subtasks.
Mail notifications to the parent/brother/subtask issues owners.
'Autosubtask' creation feature - enables automatic creation of a subtask when resolving an issue of certain entity type, for example, create a Docs issue (as a subtask) for a Wish when resolved.
Browse Product & Classification page - shows information related to product or classification, counts per components, per target version etc.
Module field - an additional list field on Product level. Can be used to represent any other Product sub-category.
Additional version fields - Target Version and Fixed In, based on the same versions list - as multi selection. Target Version is used instead of Target Milestone.
CRM Connectivity feature enables to relate bugs to specific CRM Id's (customer ticketing).
Forward Issue feature enables to "assign to" a bug, even if it's resolved, verified or closed.
Public Queries feature, enable administrator to add public queries visible by all users (or groups of users).
Customers multi selection field.
Component, Keyword & Customer helper with categorization.
'do not send mail' flag to the "Edit Issue" screen - very useful for minor changes performed on an issue.
'Auto-Reassign' feature:
automatically re-assign to the reporter when status changed to RESOLVED.
the field 'Resolver' appears in the Edit Issue screen.
automatically re-assign to the previous assignee (Resolver) when status changed to REOPENED.
Added an option to make old Components, Versions and Target versions "invisible" for new issues, but keep the history issues with correct values.
Found in Build text field that can be defined as mandatory as well.
Fixed in Build text field that can be defined as mandatory as well
QA Impact and Testing Guidelines fields.
Reopen Resolution - enables to mark the cause for bug reopening.
Last Reopen, Last Resolved, Last Verified and Last Closed information fields - appear in DB and search result page only.
A possibility to define Versions and Target Versions on Classification level - all products for the same classification get these versions & target versions.
Custom fields feature - gives an ability to add custom fields of 3 types: simple text, single selection list and multi selection list. Custom fields can have default value, can be mandatory or not; appear in the search and search result list; appear in the reports.
The following fields can be added to the mails sent by Bugzilla:
target versions
customers
crm id
priority
deadline
Added client side validation checks.
The following parameters (and functionality) are added to Bugzilla:
'use_subtasks' - enables the Subtasks functionality.
'mand_sub_sum_prefix' - make summary prefix for subtasks to mandatory.
'show_subtasks_list' - make see a subtasks list appear in the Edit Issue screen.
'mandatory_target_version' - makes 'Target Version' field mandatory only if set to 'On'.
'url_field_name' - name that will appear for URL field in all screens.
'crm_id_name' - name that will appear for CRM_ID field in all screens.
'target_fixed_in_verification' - adds verification for 'Target Version' and 'Fixed In' fields when status changed to Resolved Fixed if set to 'On' and adds verification that 'Target Version' is different than 'Fixed In' when Reopening the issue
'auto_reassign' - enables the Auto Reassign functionality
'use_found_in_build' - enables 'Found in build' field
'mandatory_found_in_build' - make 'Found in build' field mandatory
'use_fixed_in_build' - enables 'Fixed in build' field
'mandatory_fixed_in_build' - make 'Fixed in build' field mandatory
'use_qaimpact' - enables 'QA Impact' and 'Testing Guidelines' fields
