| Title | No support for Bugzilla's new per-product group controls |
| Status | closed |
| Priority | essential |
| Assigned user | Nick Barnes |
| Organization | Ravenbrook |
| Description | Bugzilla 2.17.3 introduces per-product group controls, allowing an administrator to specify which groups a bug should (or must) belong to based on its product, and also which groups a user must be in to create a bug in a given product. |
| Analysis | Newly created bugs should be placed in the mandatory groups for the product. When creating a bug, user groups must be checked according to the product. When making a change to the bug, user groups must be checked according to the product. See [1] for the schema. |
| How found | unknown |
| Evidence | [1] <http://www.ravenbrook.com/project/p4dt...er/design/bugzilla-schema/#notes-groups> |
| Observed in | 2.1.2 |
| Introduced in | 2.1.2 |
| Created by | Nick Barnes |
| Created on | 2004-06-24 14:24:40 |
| Last modified by | Nick Barnes |
| Last modified on | 2004-07-16 14:02:20 |
| History | 2004-06-24 NB Created. |
| Change | Effect | Date | User | Description |
|---|---|---|---|---|
| 97171 | closed | 2004-05-28 16:43:43 | Nick Barnes | Bugzilla 2.17.7 support: bugmail.pl replacement for processmail. Bugzilla 2.17.5 database schema changes (especially new groups system, new product and component IDs, group_control_map controls); Cache results of some database queries to speed operation with new or old schemas; Changed bug change permission rules; Clean up better when deleting a bug; Correct values in bugs_activity entries when changing user columns. |