User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 Hello, I am pretty sure that this is a duplicate (what a way to start out) but I am not positive. What I would like to be able to do is restrict people's ability to verify/close. It seems that in a sarbanes world with control mania running rampant you would want a separation of duties in regards to the qacontact and the assignee. I have tried every configuration of the member/other control but I have not accomplished what I want to do. For some of the things I am trying to get my company to do we need to be able to restrict who can verify/close bugs. Unfortunately it is not always as simple as a QA group, however this would do in a pinch it would just require many more products than we would like to use. A lot of the tickets that I would like to have go into bugzilla require that the ticket be resolved by one person and the verify/close be done by someone else. These relationships are not always the same, ie sometimes alice is the assignee and bob is the qa, at other times bob is the assignee alice is the qa. How do you guys handle this in the security process? Do you require a separation of duties? Is it on the honor system? I think that this may be a duplicate of any of the following. However a lot of the discussions/decisions/efforts on the following bugs were before a lot of the new interest in group permissions. https://bugzilla.mozilla.org/show_bug.cgi?id=90619 Restriction of user rights https://bugzilla.mozilla.org/show_bug.cgi?id=95580 The assignee has too many permissions https://bugzilla.mozilla.org/show_bug.cgi?id=49808 Added controls on verify and close Reproducible: Always Steps to Reproduce:

yeah... it's a dupe of bug 49808 *** This bug has been marked as a duplicate of 49808 ***