Bugzilla customization

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Bugzilla customization

Bobbyyy
Hi,

maybe this is the wrong group to post this question, but would you
generally recommend Bugzilla as a direct bug tracking interface for
customers (with different customer groups) in a Non-Open-Source
environment? ;-)

The problem is not setting up users (regexp is nice!) and groups
(except maybe question 4), but to prevent the reporter / viewer from
changing the bug. I've read the documentation and a lot of ng articles
dealing with restricting reporters permissions, but I couldn't achieve
the following:

1) Currently the reporter's part of CheckCanChangeField() returns "0"
for all fields. Nevertheless the reporter can add "Bug dependencies"
and "CC users" (and also add documents). Do I have to restrict this
somewhere else? (The user is not in the "canedit" group)

2) I'd like to hide all the options

- "Only users in all of the selected groups can view this bug"
(checkboxes with group names / cc)
- Leave as new
- (...)
-  Reassign bug to owner of selected component

from anybody except an admin or an authorized internal user when
viewing a bug's detail. I think I have to add some IF statement to the
template "edit.html" to do that, but I can't figure out how.

3) In general it might also be nice to "disable" the form fields
instead of telling the user that he's not allowed to change the bug
after already committing the changes. Does anyone have experience with
this?

4) And a last general question... Is it possible to set up different
groups for the same product, but to prevent the groups from viewing
each others bugs for this product?

I'd appreciate any comments or suggestions.

Best regards,
Daniel

_______________________________________________
mozilla-webtools mailing list
[hidden email]
http://mail.mozilla.org/listinfo/mozilla-webtools
Reply | Threaded
Open this post in threaded view
|

Re: Bugzilla customization

Joel Peshkin
Bobbyyy wrote:
> Hi,
>
> maybe this is the wrong group to post this question, but would you
> generally recommend Bugzilla as a direct bug tracking interface for
> customers (with different customer groups) in a Non-Open-Source
> environment? ;-)
>
Yes.  That is what drive the new groups system in 2.18

> The problem is not setting up users (regexp is nice!) and groups
> (except maybe question 4), but to prevent the reporter / viewer from
> changing the bug. I've read the documentation and a lot of ng articles
> dealing with restricting reporters permissions, but I couldn't achieve
> the following:
>
> 1) Currently the reporter's part of CheckCanChangeField() returns "0"
> for all fields. Nevertheless the reporter can add "Bug dependencies"
> and "CC users" (and also add documents). Do I have to restrict this
> somewhere else? (The user is not in the "canedit" group)
>
> 2) I'd like to hide all the options
>
> - "Only users in all of the selected groups can view this bug"
> (checkboxes with group names / cc)
> - Leave as new
> - (...)
> -  Reassign bug to owner of selected component
>
> from anybody except an admin or an authorized internal user when
> viewing a bug's detail. I think I have to add some IF statement to the
> template "edit.html" to do that, but I can't figure out how.
>
> 3) In general it might also be nice to "disable" the form fields
> instead of telling the user that he's not allowed to change the bug
> after already committing the changes. Does anyone have experience with
> this?
>

All of these are reasonable customizations that an experienced bugzilla
consultant could do for you.

> 4) And a last general question... Is it possible to set up different
> groups for the same product, but to prevent the groups from viewing
> each others bugs for this product?
>
Not very readily.  In general, you are better off keeping each customer
to their own "product"
_______________________________________________
mozilla-webtools mailing list
[hidden email]
http://mail.mozilla.org/listinfo/mozilla-webtools