m (typofix) |
|||
| Line 21: | Line 21: | ||
* Security product | * Security product | ||
- The bugs in security product are limited to only visible to security group, bug reporter and users in bug cc list. | - 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 feature, expected to be showed only in Feature product | ||
| + | - "Platform" To track which platform the 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 | ||
| + | * 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 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. | ||
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
- User is provide a copyright waiver option when submit a patch
- User is able to vote the bug, vote number indicates how many people care a specific bug
- 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".
- Normal user can propose blocker bugs for a specific release; - Users in a privileged group can approve/reject blocker bugs;
- A check box is provided to user to mark a bug as security bug;
- The bugs in security product are limited to only visible to security group, bug reporter and users in bug cc list.
- OS --> Architecture - Hardware --> Profile
- "UX Status" Track UX design status for those UX feature, expected to be showed only in Feature product - "Platform" To track which platform the 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
- Show dropdown custom fields as well as "security" checkbox in search page
- 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
- 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.
- A meanlingless text box is showed next to resolution field even the bug is not 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.