Meego Wiki
Views

MeeGo Bugzilla customization

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
 
(13 intermediate revisions not shown)
Line 1: Line 1:
-
Totally applied about 10 items to MeeGo Bugzilla to meet the MeeGo bug managment requirements.
+
== MeeGo Bugzilla Features ==
-
=== 1. Support Drupal user authentication system ===
+
Configurations and customizations have been applied to MeeGo Bugzilla to support additional features for MeeGo bug tracking.
-
* MeeGo bugzilla share the same user DB in meego.com, so there is no need to ask user to register multiple accounts
+
 
-
=== 2. Copy right waiver flag for attachment ===
+
* Support Drupal user authentication system
-
* User is able to choice copyright waiver option when submit a patch
+
** MeeGo bugzilla share the same user DB in meego.com, so there is no need to ask user to register multiple accounts
-
=== 3. Control who can change and set bug's priority ===
+
* Copyright waiver flag for attachment
-
=== 4. Enabled bug vote option ===
+
** User is provide a copyright waiver option when submit a patch
-
* User is able to vote the bug, vote number indicates how many peoples care specific bug
+
* Privilege Control for bugs' priority setting
-
=== 5. Optimized the new bug navigation web page ===
+
* Bug vote option
-
* Expand the classification MeeGo Platform in classification selection page, and list products within it. User is able to choice the product under this classification directly. This reduced one step when file new bug to most comm used classification MeeGo Platform.
+
** User is able to vote the bug, vote number indicates how many people care a specific bug
-
=== 6. Use customized flag to manage release blocker bugs ===
+
* Optimized the new bug navigation web page
-
* Normal user can propose blocker bugs;
+
** Expand the classification "MeeGo Platform" by listing products under it so that user could choose the product under this classification directly. This helps to reduce the redundant step when filing new bug to most common used classification "MeeGo Platform".
-
* Users in CCB can approve/reject blocker bugs;
+
* Use customized flag to manage release blocker bugs
-
=== 7. Customized Bugzilla new bug template for product MeeGo Platform ===
+
** Normal user can propose blocker bugs for a specific release;
-
=== 8. Set the default value for clone bug ===
+
** Users in a privileged group can approve/reject blocker bugs;
-
=== 9. Security flag ===
+
* Customized Bugzilla new bug template
-
* Added one checkbox to indentify bug's security property;
+
* Set the default value for cloned bugs
-
=== 10. Security product ===
+
* Security flag
-
* The bugs in security product can be seen only to Security group, bug reporter and user in bug cc list.
+
** A check box is provided to user to mark a bug as security bug;
 +
* Security product
 +
** The bugs in security product are limited to only visible to security group, bug reporter and users in bug cc list.
 +
* Field name display renaming
 +
** OS --> Architecture
 +
** Hardware --> Profile
 +
* New custom fields
 +
** "UX Status" Track UX design status for those UX features. This field is expected to be showed only in feature products
 +
** "Platform" To track which platform this bug is found. It's 1:M mapping relationship with Profile field
 +
** "Update Release" To track which update release number the bug is expected to be fixed
 +
** "Triaged By" To track who made the triage to the bug
 +
* Show custom fields in advanced page
 +
** Show dropdown custom fields as well as "security" checkbox in search page
 +
* Per product configurable priority change control group
 +
** This is the enhanced patch for customization "Privilege Control for bugs' priority setting"
 +
** Admin is able to configure which group is able to change priority of given product from product administration page
 +
* Admin configurable release blocker flag rendering
 +
** This is the enhanced patch for customization "Use customized flag to manage release blocker bugs"
 +
** Admin is able to configure which flag need to be showed as Release Blocker fashion. And most of hardcode is removed
 +
* Known bug fixes for MeeGo 3.6 Bugzilla upgrading
 +
** A meanlingless text box is showed next to resolution field even the bug is not the duplicated resolution
 +
** RESOVED REJECTED feature is not showed correctly for users only granted with Feature Owners privilege
 +
** Bugzilla should disallow to submit bug specific status to a feature and vice verse to submit feature specific status to a bug
 +
* Toolkits for feature management
 +
** Feature import tool to bulk load features from xls
 +
** Export features' description to csv file
 +
 
 +
[[Category:QA]]

Latest revision as of 10:11, 11 July 2011

MeeGo Bugzilla Features

Configurations and customizations have been applied to MeeGo Bugzilla to support additional features for MeeGo bug tracking.

  • Support Drupal user authentication system
    • MeeGo bugzilla share the same user DB in meego.com, so there is no need to ask user to register multiple accounts
  • Copyright waiver flag for attachment
    • User is provide a copyright waiver option when submit a patch
  • Privilege Control for bugs' priority setting
  • Bug vote option
    • User is able to vote the bug, vote number indicates how many people care a specific bug
  • Optimized the new bug navigation web page
    • Expand the classification "MeeGo Platform" by listing products under it so that user could choose the product under this classification directly. This helps to reduce the redundant step when filing new bug to most common used classification "MeeGo Platform".
  • Use customized flag to manage release blocker bugs
    • Normal user can propose blocker bugs for a specific release;
    • Users in a privileged group can approve/reject blocker bugs;
  • Customized Bugzilla new bug template
  • Set the default value for cloned bugs
  • Security flag
    • A check box is provided to user to mark a bug as security bug;
  • Security product
    • The bugs in security product are limited to only visible to security group, bug reporter and users in bug cc list.
  • Field name display renaming
    • OS --> Architecture
    • Hardware --> Profile
  • New custom fields
    • "UX Status" Track UX design status for those UX features. This field is expected to be showed only in feature products
    • "Platform" To track which platform this bug is found. It's 1:M mapping relationship with Profile field
    • "Update Release" To track which update release number the bug is expected to be fixed
    • "Triaged By" To track who made the triage to the bug
  • Show custom fields in advanced page
    • Show dropdown custom fields as well as "security" checkbox in search page
  • Per product configurable priority change control group
    • This is the enhanced patch for customization "Privilege Control for bugs' priority setting"
    • Admin is able to configure which group is able to change priority of given product from product administration page
  • Admin configurable release blocker flag rendering
    • This is the enhanced patch for customization "Use customized flag to manage release blocker bugs"
    • Admin is able to configure which flag need to be showed as Release Blocker fashion. And most of hardcode is removed
  • Known bug fixes for MeeGo 3.6 Bugzilla upgrading
    • A meanlingless text box is showed next to resolution field even the bug is not the duplicated resolution
    • RESOVED REJECTED feature is not showed correctly for users only granted with Feature Owners privilege
    • Bugzilla should disallow to submit bug specific status to a feature and vice verse to submit feature specific status to a bug
  • Toolkits for feature management
    • Feature import tool to bulk load features from xls
    • Export features' description to csv file
Retrieved from "http://wiki.meego.com/MeeGo_Bugzilla_customization"
Personal tools