Using group to give "edit components" rights and "use for bugs"
I have a product, and I want to give the rights to adminster that
product (edit components and so on) to another person. According to
the documentation (3.4.4, 3.15), using a group seems to be the proper
way to do this, so I created a group for the purpose.
Now, the documentation says (section 3.4.4) that "After selecting the
"Edit Group Access Controls" link from the "Edit Product" page, a
table containing all user-defined groups for this Bugzilla
installation is displayed.". So, I did select "Edit Group Access
Controls" for the product, and expected my group to show up. But the
problem is that my group is _not_ displayed. (And therefore, I can
not use for assigning control over the product either.)
The group not being displayed seems to be related to whether the "use
for bugs" is ticked for the group or not. If this is ticked, the
group is displayed. If it is not, the group is not displayed. It may
be the case that I do not understand this "use for bugs" tick marks.
I am not going to use this group for bugs, I am only going to use it
to grant the "edit components" rights for the product to another
person. So therefore I can not see why I should tick the "use for
* Why isn't my group being displayed if "use for bugs" is not ticked?
* What is really the meaning of the "use for bugs" tick mark? (I find
the documentation unclear on this point.)
* Why must the group be marked "use for bugs" when all I want is to
use it to give out the rights to edit the components of the product?
Re: Using group to give "edit components" rights and "use for bugs"
2009/7/15 Asbjørn <[hidden email]>:
> * Why isn't my group being displayed if "use for bugs" is not ticked?
I think this has historical reasons. Older versions of Bugzilla didn't
offer the possibility to have editcomponents (and friends) to be set
per-product. All you had were the bug access controls. The "use for
bugs" naming stems from that time, and is misleading now.
Maybe there is already a bug for this. If there isn't, I think you
should file it.
> * What is really the meaning of the "use for bugs" tick mark? (I find
> the documentation unclear on this point.)
From an administrator's point of view, the meaning is really whether
or not it shows up in the access control list on products.