Update documentation on group controls

RESOLVED FIXED in Bugzilla 2.18

Status

()

defect
P3
major
RESOLVED FIXED
16 years ago
7 years ago

People

(Reporter: bugreport, Assigned: bugreport)

Tracking

2.17.3
Bugzilla 2.18
All
Other
Bug Flags:
approval +

Details

Attachments

(1 attachment, 1 obsolete attachment)

Assignee

Description

16 years ago
 
Assignee

Updated

16 years ago
Status: NEW → ASSIGNED
Priority: -- → P3
Hardware: PC → All
Target Milestone: --- → Bugzilla 2.18
Assignee

Comment 1

16 years ago
Posted patch New Groups security stuff (obsolete) — Splinter Review
Assignee

Updated

16 years ago
Attachment #143920 - Flags: review?
Assignee

Updated

16 years ago
Whiteboard: [wanted for 2.18rc1]
Enhancements which don't currently have patches on them which are targetted at
2.18 are being retargetted to 2.20 because we're about to freeze for 2.18. 
Consideration will be taken for moving items back to 2.18 on a case-by-case
basis (but is unlikely for enhancements)
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
I'd say this is a fairly major doc bug. And it has a patch.

Gerv
Severity: enhancement → major
Preliminarily moving all docs bugs to 2.18, we should make a valiant attempt to
have the docs as up-to-date as possible when 2.18 releases.
Target Milestone: Bugzilla 2.20 → Bugzilla 2.18
> Otherwise, the group can still be used to organize groups of users without 
> being used to control access to bugs.

You need to be more specific here. What sort of thing does this mean?

+      On the product edit page, there is a page to edit the 
+      <quote>Group Controls</quote> 
+      for a product and determine which groups are applicable, default, 
+      and mandatory for each product as well as controlling entry 
+      for each product and being able to set bugs in a product to be 
+      totally read-only unless some group restrictions are met. 

This is a pretty horrible sentence... Why not just say:

On the product edit page, there is a link to edit the Group Controls for a
product. This allows you to configure how a group relates to a particular
product, in a number of different ways. <list them>

If there are cases where a user can check a group and click commit, thereby
hiding the bug from themselves, you need to explain that.

> inacessable
> relevent

Typos.

This is all OK so far as it goes, but the whole thing is still really hard to
understand. It's also not clear why groups are so closely linked to products -
this needs some explanation. I, for one, when I came up with a groups use
scenario for a company, just wanted to isolate groups of people from one another
without regard to the product concerned, and couldn't figure out how to do that.

Gerv
Assignee

Updated

16 years ago
Attachment #143920 - Flags: review?
Assignee

Comment 6

16 years ago
OK, this addresses Gerv's comments.

There is a lot more that could be said about this topic, but that is a
different bug.
Attachment #143920 - Attachment is obsolete: true
Assignee

Updated

16 years ago
Attachment #144203 - Flags: review?(gerv)
Comment on attachment 144203 [details] [diff] [review]
v2 including Gerv's comments

r=gerv.

Gerv
Attachment #144203 - Flags: review?(gerv) → review+
Flags: approval? → approval+
Assignee

Comment 8

16 years ago
Checked in
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Whiteboard: [wanted for 2.18rc1]
Assignee

Comment 9

16 years ago
*** Bug 228645 has been marked as a duplicate of this bug. ***
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.