Diff for "BugSupervisors"

Not logged in - Log In / Register
Differences between revisions 1 and 3 (spanning 2 versions)
⇤ ← Revision 1 as of 2009-11-12 15:41:52 →
Size: 409
Editor: Fd16c
Comment:
← Revision 3 as of 2010-07-07 19:40:14 → ⇥
Size: 1269
Editor: 201-74-139-114-sj
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
The bug supervisor is a person or team that is responsible for bug
management in a project or in a distribution.		 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.)

 * 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.)

 * 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.)
Line 8: Line 21:
  * Only the project/distribution owner or members of the team that own
    the project/dsitribution may appoint the bug supervisor.		   * Only the project/distribution owner may appoint the bug supervisor.

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.)
  • 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.)
  • 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.

BugSupervisors (last edited 2012-09-06 16:43:00 by pool-108-28-25-212)