From 849908055772cf8d7bfceda4af5cace7a103cddb Mon Sep 17 00:00:00 2001 From: "mozilla%colinogilvie.co.uk" <> Date: Fri, 4 Apr 2008 11:48:08 +0000 Subject: Bug 397665: "Assigning Group Controls to Products" doesn't explain editcomponents, canconfirm, editbugs Patch by Sam Folk-Williams ; r=me, r=lpsolit --- docs/en/xml/administration.xml | 230 ++++++++++++++++++++++++++--------------- 1 file changed, 148 insertions(+), 82 deletions(-) diff --git a/docs/en/xml/administration.xml b/docs/en/xml/administration.xml index e07c2ec41..a0c7a7c8b 100644 --- a/docs/en/xml/administration.xml +++ b/docs/en/xml/administration.xml @@ -673,43 +673,165 @@ Products - tend to represent real-world shipping products. E.g. if your company makes computer games, - you should have one product per game, perhaps a "Common" product for - units of technology used in multiple games, and maybe a few special - products (Website, Administration...) + you should have one product per game, perhaps a + Common product for units of technology used + in multiple games, and maybe a few special products + (Website, Administration...) + - Many of Bugzilla's settings are configurable on a per-product - basis. The number of "votes" available to users is set per-product, - as is the number of votes - required to move a bug automatically from the UNCONFIRMED status to the - NEW status. + + Many of Bugzilla's settings are configurable on a per-product + basis. The number of votes available to + users is set per-product, as is the number of votes + required to move a bug automatically from the UNCONFIRMED + status to the NEW status. + - To create a new product: + + To create a new product: + - Select "products" from the footer + + Select Adminstration from the footer and then + choose Products from the main administration page. + - Select the "Add" link in the bottom right + + Select the Add link in the bottom right. + - Enter the name of the product and a description. The - Description field may contain HTML. + + Enter the name of the product and a description. The + Description field may contain HTML. + - Don't worry about the "Closed for bug entry", "Maximum Votes - per person", "Maximum votes a person can put on a single bug", - "Number of votes a bug in this Product needs to automatically get out - of the UNCONFIRMED state", and "Version" options yet. We'll cover - those in a few moments. - + +
+ Assigning Group Controls to Products + + On the Product Edit page, + there is a link called + Edit Group Access Controls. + The settings on this page control the relationship + of the groups to the product being edited. + + + Groups may be applicable, default, and + mandatory for each product. Groups can also control access + to bugs for a given product, or be used to make bugs + for a product totally read-only unless the group + restrictions are met. + + + If any group has Entry selected, then the + product will restrict bug entry to only those users + who are members of all the groups with + Entry selected. + + + If any group has Canedit selected, + then the product will be read-only for any users + who are not members of all of the groups with + Canedit selected. ONLY users who + are members of all the Canedit groups + will be able to edit. This is an + additional restriction that further limits + what can be edited by a user. + + + The following settings let you + choose privileges on a per-product basis. + This is a convenient way to give privileges to + some users for some products only, without having + to give them global privileges which would affect + all products. + + + Any group having editcomponents + selected allows users who are in this group to edit all + aspects of this product, including components, milestones + and versions. + + + Any group having canconfirm selected + allows users who are in this group to confirm bugs + in this product. + + + Any group having editbugs selected allows + users who are in this group to edit all fields of + bugs in this product. + + + The MemberControl and + OtherControl fields indicate which + bugs will be placed in this group according + to the following definitions. + + + For each group, it is possible to specify if + membership in that group is: + + + + + Required for bug entry. + + + + + Not applicable to this product(NA), + a possible restriction for a member of the + group to place on a bug in this product(Shown), + a default restriction for a member of the + group to place on a bug in this product(Default), + or a mandatory restriction to be placed on bugs + in this product(Mandatory). + + + + + Not applicable by non-members to this product(NA), + a possible restriction for a non-member of the + group to place on a bug in this product(Shown), + a default restriction for a non-member of the + group to place on a bug in this product(Default), + or a mandatory restriction to be placed on bugs + in this product when entered by a non-member(Mandatory). + + + + + Required in order to make any change + to bugs in this product including comments. + + + + These controls are often described in this order, so a + product that requires a user to be a member of group "foo" + to enter a bug and then requires that the bug stay restricted + to group "foo" at all times and that only members of group "foo" + can edit the bug even if they otherwise could see the bug would + have its controls summarized by... + +foo: ENTRY, MANDATORY/MANDATORY, CANEDIT + + +
+ + +
@@ -1645,70 +1767,14 @@
-
- Assigning Group Controls to Products - - On the product edit page, there is a page to edit the - Group Controls - for a product. This allows you to - configure how a group relates to the product. - Groups may be applicable, default, - and mandatory as well as used to control entry - or used to make bugs in the product - totally read-only unless the group restrictions are met. - - - - For each group, it is possible to specify if membership in that - group is... - - - - - required for bug entry, - - - - - Not applicable to this product(NA), - a possible restriction for a member of the - group to place on a bug in this product(Shown), - a default restriction for a member of the - group to place on a bug in this product(Default), - or a mandatory restriction to be placed on bugs - in this product(Mandatory). - - - - - Not applicable by non-members to this product(NA), - a possible restriction for a non-member of the - group to place on a bug in this product(Shown), - a default restriction for a non-member of the - group to place on a bug in this product(Default), - or a mandatory restriction to be placed on bugs - in this product when entered by a non-member(Mandatory). - - - - - required in order to make any change - to bugs in this product including comments. - - - - These controls are often described in this order, so a - product that requires a user to be a member of group "foo" - to enter a bug and then requires that the bug stay restricted - to group "foo" at all times and that only members of group "foo" - can edit the bug even if they otherwise could see the bug would - have its controls summarized by... - -foo: ENTRY, MANDATORY/MANDATORY, CANEDIT - - + Assigning Group Controls to Products + + For information on assigning group controls to + products, see . +
+
Common Applications of Group Controls
-- cgit v1.2.3-24-g4f1b