286040 - Confusing with how to setup the group security

Status: RESOLVED DUPLICATE of bug 281809

(Bugzilla :: Administration, task)

Description

[Bo Zhang]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; Maxthon)
Build Identifier: 

I'm using Bugzilla 2.19.2, however, it's still confusing to set up the group 
security as the URL states.

For example, I have 
ProductA and ProductB
GroupA, GroupB, GroupC, GroupX, and GroupY

I want
ProductA can be available (read/write) to GroupA~C but inaccessable/invisiable 
to GroupX
ProductB can be available (read/write) to GroupY but inaccessable/invisiable  
to GroupA~C/X

How can do it? It's very confusing about the Entry, Canedit, and 
Shown/Default/Mandatory/NA. It's hard to tell the difference from the URL.

In addition, what if I want a bug#222 in ProdcutA can be visiable/writable by 
GroupA and GroupB, how can I set it? It's also very confusing for
1. "Only users in all of the selected groups can view this bug: 
(Unchecking all boxes makes this a more public bug.)" in a bug page
It sounds the logic is reversed here. So for bug#222, that would be nice if 
change it to "Only users in ANY of the selected groups can view this bug".
2. "Group Access: Can turn this bit on for other users" at the Edit User page.
Why other user pops up here? What's the relationship to the user under edition?

Thanks,
Bo



Reproducible: Always

Comment 1

[Shane H. W. Travis]

This is really a documentation bug, since the information you seek would be 
contained in more detail in the docs. 

I have already noticed that, while there is some information on groups in the 
documentation, it could do with improving and expanding. I am marking this bug 
as a duplicate of that one.



*** This bug has been marked as a duplicate of 281809 ***

Comment 2

[Bo Zhang]

can you please kindly answer my questions?

thanks a lot

Comment 3

[Marc Schumann [:Wurblzap]]

Bugzilla is for bugs :)
Please refer to http://www.bugzilla.org/support/ to find out where to ask
support questions.

*** This bug has been marked as a duplicate of 281809 ***