<html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hi All, I've hacked bugzilla a bit but it needs some thorough testing before we commit it to our actual bugzilla instance. What I've done: <ul> <li>Locked the following fields to anyone that does not belong to group "contributors" or are assigned the bug</li> <ul> <li>QA Contact;</li> <li>Assignee;</li> <li>Severity</li> <li>Priority</li> </ul> </ul> To test: <ol> <li>Head over to our test instance of bugzilla: <a class="moz-txt-link-freetext" href="https://bugzilla-test.documentfoundation.org/">https://bugzilla-test.documentfoundation.org/</a></li> <ol> <li>As a starting point you can check by going here: <a class="moz-txt-link-freetext" href="https://bugzilla-test.documentfoundation.org/show_bug.cgi?id=89058">https://bugzilla-test.documentfoundation.org/show_bug.cgi?id=89058</a> (you should see fields locked out)</li> </ol> <li>Contact me to get added to contributor group (include your email that you use on bugzilla)</li> <li>Create a test login that won't have any privileges</li> </ol> Now you should be able to report bugs and compare what happens with your two users (the one in contributors and the new test account you create) What Needs Testing <ol> <li>Basically do everything you could think of, create a bug with both accounts, compare your access, change status (NEW, FIXED, ETC....), see what impact you see, report any issues to me directly (please include repro steps to save me time :) )</li> </ol> Goal: *We hope to abandon MAB once and for all and replace with objectively accurate priorities/severity *Being added to "contributor" group will be *very* easy, we'll document it on the wiki but basically it will be emailing the QA list with a generic email that requests being added. We don't want this to be a hurdle beyond users manipulating bug priority/severity. Contact me with any questions/concerns Thanks all Best, Joel </body> </html>