386023 - Assign a bug to a workgroup

Status: RESOLVED DUPLICATE of bug 98310

(Bugzilla :: Bugzilla-General, enhancement)

Description

[George Fischhof]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; hu; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4
Build Identifier: 


A concept that I've seen on a number of other bug tracking and ticket tracking
systems that Bugzilla is missing is the concept of "workgroups".

When a new bug is opened, the bug does not get assigned to a specific person,
but to a workgroup, or a department.  Each workgroup would have an owner, or a
team leader, who could decide the notification method for new tickets in that
workgroup.  For example, unassigned tickets could have their mail sent to a
specific person (the team leader, or perhaps a delegate), or they might want
everyone in the workgroup to get mail on it.

When someone takes on the bug, it's THEN that the bug is actually assigned to a
specific person.  It could be the team leader delegating the bugs to various
team members, or it could be a team member who happened to see the bug and
decides to jump in and take it, or however.  Once the bug is owned, the mail
would only go to the owner.

Workgroups would only define groups of people.  The same workgroup could
conceivably own more than one component.

There should be a tier of responsibility within the workgroup (regular team
members, and the team leader, at a minimum, and perhaps who the manager or
director for that team is).

This would require a new status (perhaps called OWNED) that would take the place
of the current use for ASSIGNED (meaning the bug actually belongs to a person)
and ASSIGNED would mean that the bug was assigned to a workgroup.

Another benefit of this system is that it would allow a popup menu of assignees
(which would contain the workgroups, and not the potential owners) because the
list would likely be small enough to be manageable.


Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Frédéric Buclin]

There is a name for what you did: plagiarism!

Comment 2

[Max Kanat-Alexander]

(In reply to comment #1)
> There is a name for what you did: plagiarism!

  It's not plagiarism to take concepts and user interfaces from other programs, unless those concepts are patented.

  After all, people take ideas from Bugzilla all the time, and you don't see us suing them or complaining a lot.

Comment 3

[Max Kanat-Alexander]

Oh, nevermind. :-) Jeez!

Comment 4

[George Fischhof]

Hi!

You are right. But the description was so good, that I did not want to make it worse with my rewording. :-)
Bug 98310 is reported to Bugzilla 2.16. And I wanted to report it v3.0. We currently use another bugtracker system, and we want to change to Bugzilla now. 
But grouping feature is very important for us (we are working in teams (groups)). I used a ticketing system before and it was very good. But simple ticketing systems does not good for bugtracking. There is a possibility to use a bugtracker and a ticketing system together, but it consumes a lot of work. 
Therefore I started to search for appropriate bugtracking system, and found that  Bugzilla is very good, but unfortunately it has no grouping function.
I think with this function Bugzilla would be the best.

Regards,
George

Comment 5

[timeless]

George: the version of a bug is the version where it was found. a bug can't be fixed in the version it's found in, it will be fixed in some later release. that bug might be fixed for 3.2 or 3.4, but it won't be fixed in 2.16.x or anything.

and note that incomplete is designed to mean that a bug doesn't have enough details for an engineer to work on it. a stolen well reported bug can't possibly fall into that category.