Archive:Bugzilla administrator rights policy
Please note: This page is kept for historical reasons and may be out-of-date or inaccurate.
Due to Wikimedia's move from Bugzilla to Phabricator in November 2014 this page has become partially outdated. Also see mw:Phabricator/Permissions#Administrators.
This policy or procedure is maintained by the Wikimedia Foundation and applies to Foundation activities.
Please note that in the event of any differences in meaning or interpretation between the original English version of this content and a translation, the original English version takes precedence.
This document describes when to hand out administrator rights in Wikimedia Bugzilla.
Some users at bugzilla.wikimedia.org have administrator rights and hence more powers than other users. Without guidelines why a user is an administrator, this can create mistrust. Furthermore, having a large number of administrators can create coordination issues.
When none of the tasks listed below under "Tasks which require being an administrator" are to be executed by a specific Bugzilla user, a combination of other, more specific Bugzilla group memberships should be handed out instead of handing out admin and/or editusers group membership. This also helps avoiding a large number of Bugzilla administrators and related coordination issues.
If admin group membership is handed out to individuals who are not employees of the Wikimedia Foundation it is required to sign an indefinite non-disclosure agreement first, due to legal requirements (e.g. access to security bugs).
Tasks which require being an administrator
Membership in the Bugzilla admin group is required for the following tasks:
Bugzilla in general
- editing or blocking Bugzilla accounts, e.g. in case of violations against the code of conduct policy (this is inherited from editusers group membership: editusers group membership de facto means admin group membership, as an account with editusers group membership can edit his/her account and set admin group membership.)
- deleting attachments (instead of just marking them as private)
- editing Bugzilla field values and custom fields
- editing the bug status workflow
- viewing the generated SQL query by using the &debug=1 URL parameter
The list above is not necessarily complete. (Thanks to Byran Jones (:glob) for input.)
Specific Wikimedia Bugzilla configuration
- Marking comments and attachments as private and accessing comments and attachments marked as private requires membership in the insidergroup group. The insidergroup group is currently (2013-05-26) set to consist of the admin and security groups.
- In order to be able to edit/ban Bugzilla accounts and/or hide Bugzilla comments in emergency cases (e.g. spamming over public holidays when most people are not on duty), the Wikimedia Foundation Operations team has a dedicated Bugzilla account.