From 1726ea22f23a446cc779a289804ecbe9e45b9043 Mon Sep 17 00:00:00 2001 From: "mozilla%colinogilvie.co.uk" <> Date: Sat, 19 Jan 2008 23:24:36 +0000 Subject: Bug 310400: Explain (Document) how permissions are handled on Bugzilla Patch by Sam Folk-Williams ; r=me --- docs/xml/customization.xml | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) (limited to 'docs/xml/customization.xml') diff --git a/docs/xml/customization.xml b/docs/xml/customization.xml index 90d2d6208..bb89cb12b 100644 --- a/docs/xml/customization.xml +++ b/docs/xml/customization.xml @@ -688,7 +688,7 @@ versions, and you upgrade. - + Companies often have rules about which employees, or classes of employees, are allowed to change certain things in the bug system. For example, @@ -697,6 +697,16 @@ designed to make it easy for you to write your own custom rules to define who is allowed to make what sorts of value transition. + + + By default, assignees, QA owners and users + with editbugs privileges can edit all fields of bugs, + except group restrictions (unless they are members of the groups they + are trying to change). Bug reporters also have the ability to edit some + fields, but in a more restrictive manner. Other users, without + editbugs privileges, can not edit + bugs, except to comment and add themselves to the CC list. + For maximum flexibility, customizing this means editing Bugzilla's Perl -- cgit v1.2.3-24-g4f1b