30189 - Ability to restrict visibilty of values in the Version field to certain groups

Status: RESOLVED WONTFIX

(Bugzilla :: Administration, task, P4)

Description

[Dave Miller [:justdave]]

It would be cool to be able to hide a given product, or a version of a product, 
so that a user would need to be logged in and have access to a certain group 
before they could even see that the product existed.  A good way to implement 
this would be to add a groupset column to the versions table, and if there are no 
versions of a given product that the user would have access to according to that 
groupset, then the entire product is not even shown.  Also, this groupset would 
be used for the default viewability of the bug itself (see bug 30187).

I'm playing around with this myself already, if I get it working I'll post the 
diffs here.  If anyone has comments on this I'd appreciate them though.

Comment 1

[Terry Weissman]

[e-mail] is the new owner of Bugzilla and Bonsai.  (For details,
see my posting in netscape.public.mozilla.webtools,
news://news.mozilla.org/38F5D90D.F40E8C1A%40geocast.com .)

Comment 2

[Dave Miller [:justdave]]

Ability to hide a product based on group was added in bug 25010.

Still need a way to hide a version based on group, so leaving this open.

Comment 3

[Stephan Niemz]

Adding default QA contact to all open Webtools/Bugzilla bugs lacking one.
Sorry for the spam.

Comment 4

[Dave Miller [:justdave]]

Moving to real milestones...

Comment 5

[Hixie (not reading bugmail)]

Imagine you set value V of field F to be only visible by people in group G.
Bug B has field F set to value V. Person P (is this getting complicated enough
yet?) has access to bug B and field F but is not in group G, so doesn't have
access to value V.

What should he see?

Comment 6

[Hixie (not reading bugmail)]

Taking all Bugzilla 3.0 bugs -- congratulations to MattyT for the triage, it
really was spot on. Note: I may end up pushing some of these bugs back to 3.2,
we'll see. However, I believe all these bugs should just fall out of the 
redesign. Let's hope I'm right!

(Note: I'm also resetting the priority field to "---" so that I can retriage any
that I consider important or likely to be dropped.)

Comment 7

[Dave Miller [:justdave]]

The Bugzilla 3 component is going away.  We're going to depend on the Milestones 
for this.  At the time this component was created, we didn't have milestones for 
Bugzilla.

Comment 8

[Bradley Baetz (:bbaetz)]

clarifying summary - we can already do this to products

Comment 9

[Hixie (not reading bugmail)]

Bailing on Bugzilla 3.0 due to too many other commitments.

Comment 10

[Max Kanat-Alexander]

Now that a real Bugzilla 3.0 is going to be released, this Bugzilla3 bug is no longer correctly targeted--this bug is actually unlikely to be implemented in Bugzilla 3.0.

Comment 11

[Frédéric Buclin]

justdave, you didn't provide any real use case where this would be useful, and even bug 372978 doesn't provide any good reason either. So that's WONTFIX to me.