Last modified: 2014-01-13 16:00:46 UTC
Having talked to a number of Wikimedia (Foundation) development teams in the past, two or three teams that do not primarily use Bugzilla but other tools often mentioned that anybody can change the "Priority" field in of bug reports, so that priorities might not reflect anymore what the team really plans to work on. This does not mean that it is planned to introduce restrictions when it comes to setting/changing priorities of bug reports; I'd just like to drop some collected information here that might help evaluating later (if needed and wanted). Upstream ticket: https://bugzilla.mozilla.org/show_bug.cgi?id=372017 General upstream recommendations: https://wiki.mozilla.org/Bugzilla:FAQ#Can_I_restrict_a_user.27s_ability_to_edit_certain_bug_fields.3F http://www.bugzilla.org/docs/tip/en/html/cust-change-permissions.html using check_can_change_field() RedHat patch (against an old Bugzilla 3.x version) globally based on group: https://bugzilla.redhat.com/show_bug.cgi?id=495985#c25 MeeGo extension (against Bugzilla 3.6; per product configurable priority change control group, Admin is able to configure which group is able to change priority of given product from product administration page): http://gitorious.org/meego-bugzilla/priority-chgctl/commit/50f907c5319a9065b835ca5e3b5340808d9ba614 http://gitorious.org/meego-bugzilla/priority-chgctl/commit/ef35841f75dd1c4f74a6135fd196addb726e0e10 http://wiki.meego.com/MeeGo_Bugzilla_customization
Sumana brought up that this would need to be very fine-grained as we have lots of Bugzilla components that are NOT led by WMF developers but community.
I think it makes sense to restrict the priority fields to the actual maintainers of the component, since they are most likely the ones that will work on these tasks. I don't see this as a WMF vs Others problem, but as a Maintainers vs Others problem. The fact that WMF employees happen to be Maintainers of some components doesn't make any difference. The conclusion is that any solution should be applicable at the component level.
I took a quick look again today if this (to some extend) could also be investigated by using group permissions instead. http://www.bugzilla.org/docs/tip/en/html/products.html#product-group-controls allows restrictions per product by defining group memberships since https://bugzilla.mozilla.org/show_bug.cgi?id=189627 got fixed in http://bzr.mozilla.org/bugzilla/trunk/revision/4674 . The related documentation generally sucks ( https://bugzilla.mozilla.org/show_bug.cgi?id=481859 ) and I haven't experimented with this so far.
