216148 - possible bug/group restrictions are not sufficient

Status: RESOLVED WORKSFORME

(Bugzilla :: Bugzilla-General, enhancement)

Description

[Daniel Raichle]

It should be possible to handle the following use case in bugzilla:
There are three roles:
- developers
- customer-A
- customer-B

Only a customer or a developer should be able to enter a new bug. All other
bugzilla users should not even see this product.

If customer A enters a new bug. It should be accessible for the customer-A-group
and the developers-group only. Similar if customer-B enters a bug. Note: a
customer should not have the right to make the bug accessible for the other
customer.

If a developer enters a bug, he should be able to decide if the bug should be
accessible only for developers or if it should be accessible for developers and
one of the customers or if it should be accessible for developers and all customers.

If a customer entered a bug, a developer should be able to give access to other
customers, too.

It should be possible to extend this scenario with some extra customers.

Comment 1

[Dave Miller [:justdave]]

Everything you're asking for already works.  See
http://www.bugzilla.org/discussion.html for places you can ask for help setting
it up if you can't figure it out from the docs.

Comment 2

[Daniel Raichle]

Sorry, but I think you're wrong.

I thought of 4 different groups for this product with the following settings:
- base-group: Mandatory/Mandatory, ENTRY (customer-A, customer-B and developers
would be in this group. So only those 3 roles could see this product and these bugs)
- developers-group: Default/NA (developers are in this group)
- customer-A: Mandatory/Mandatory (customer-A is in this group, but the
developers must be in this group, too, because they would not be able to access
a bug entered by customer-A)
- customer-B: Mandatory/Mandatory (customer-B and developers are in this group,
see above)

Now a developer wants to enter a bug which is accessible for the developers and
customer-A => this is not possible because of the mandatory settings of the two
customer groups. This bug would be assigned to the groups: base-group,
developers, customer-A, customer-B.

Now you could say that I shouldn't use Mandatory/Mandaytory for the
customer-groups but then I have the problem that customer-A can enter a bug
which is accessible for customer-B.

We thought about some other settings, too, but we didn't find anything that works.

Sorry for reopening the bug, but I'm very sure that it does not work. 
I would have written something in the newsgroups but I cannot access it because
I'm sitting behind a very restrictive firewall/proxy here at my company.

Comment 3

[Dave Miller [:justdave]]

You can't send/receive email?  It has a mail gateway (which I recommend - I hate
NNTP personally)

Joel, thoughts?

Comment 4

[Joel Peshkin]

What you need to do is....

Product A - for customer A
Product B - for customer B
Product X - for internal and general use

Groups:
Apeople - customer A people
Bpeople - customer B people
Xpeople - your own development staff

Aaccess - composed of everyone in Apeople PLUS everyone in Xpeople
Baccess - composed of everyone in Bpeople PLUS everyong in Xpeople
Xaccess - composed of everyone in Apeople PLUS everyone in Bpeople PLUS everyone
in Xpeople

Product A gets....
Aaccess ENTRY,MANDATORY/MANDATORY, CANEDIT
Xpeople Shown/NA

Product B gets...
Baccess ENTRY, MANDATORY/MANDATORY, CANEDIT
Xpeople Shown/NA

Product X gets...
Xaccess MANDATORY/MANDATORY
Xpeople ENTRY, DEFAULT/NA, CANEDIT

Comment 5

[Marc Schumann [:Wurblzap]]

I'd say this can either be RESOLVED WORKSFORME per comment 4 or marked as a
duplicate of bug 281926, what do you think?

Comment 6

[Joel Peshkin]

Yes.  I think 6 months of limbo is enough.