Size: 1269
Comment:
|
Size: 1118
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 11: | Line 11: |
* Automatically subscribed to all bugs in that project/distro. (Other users can subscribe to bug mail, or can subscribe to particular bugs.) * Can see all private bugs in that project/distro. (Other users can only see those they're subscribed to.) |
|
Line 24: | Line 20: |
* Are automatically subscribed to private bugs when the project has the private bugs feature enabled, |
Bug Supervisors
The bug supervisor is a person or team that is responsible for bug management in a project or in a distribution.
A common pattern is to create a project-qa team, containing the developers and other people who want to help with bug management. For very large projects the bug supervisor may be only a subset of the developers.
Being bug supervisor (or a member of a bug supervisor team) has the following powers:
- Can set bugs to Triaged state, indicating that the project team has accepted they will work on the bug. (Other users can only set it to Confirmed.)
- Cannot target bugs to a milestone or to a series. (Only project drivers/owners/release managers can do this.)
- Can assign bugs to other people. (Others can only assign bugs to themselves.)
There are two restrictions when you appoint a bug supervisor:
- Only the project/distribution owner may appoint the bug supervisor.
- You can only appoint yourself or a team which you administer.
- Are automatically subscribed to private bugs when the project has the private bugs feature enabled,