BMO/new-security-group: Difference between revisions
< BMO
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
** If the requester wanted an automatic CC when a bug is placed into the group, update <tt>%group_to_cc_map</tt> | ** If the requester wanted an automatic CC when a bug is placed into the group, update <tt>%group_to_cc_map</tt> | ||
* Security groups | * Security groups are rarely granted explicitly into. Normally the groups membership is determined by inheritance from other groups. | ||
Revision as of 14:42, 2 May 2012
Adding a new security group
These steps need to be implemented when adding a new "security" group to BMO after the group has been created on BMO:
- Add code to extensions/BMO/lib/Data.pm that accomplish the following:
- If the group is to be used as the default security group for a product (ie. it will be used when the user checks "Many users could be harmed by this security problem: it should be kept hidden from the public until it is resolved"):
- Add the group to %product_sec_groups (this establishes the mapping)
- Add the group to %always_fileable_group (this ensures all users can file bugs into this group)
- If the requester wanted an automatic CC when a bug is placed into the group, update %group_to_cc_map
- If the group is to be used as the default security group for a product (ie. it will be used when the user checks "Many users could be harmed by this security problem: it should be kept hidden from the public until it is resolved"):
- Security groups are rarely granted explicitly into. Normally the groups membership is determined by inheritance from other groups.