370171 - Let me promote myself as a global watcher

Status: NEW

(Bugzilla :: Email Notifications, enhancement)

Description

[Frédéric Buclin]

I want to be able to track all status changes of bugs being in the Bugzilla and Doctor products. I first thought about watching a global watcher, but this doesn't work. The reason is probably because the global watcher has no role for these bugs. So my first thought was: this is either a bug or let me promote myself as a global watcher.

Then I thought about it a bit more and realized that I would see *all* bugs, including those I don't care about. So my second thought is that global watchers should have the ability to restrict the products (and components?) to watch, and so having something similar to the inclusion/exclusion lists we have for flag types.

My final thought is that the 'globalwatcher' parameter should be removed (as you would now be able to promote yourself as a global watcher) and replaced either by a boolean 'allow_global_watching' parameter or by a 'globalwatcher_group' drop down menu letting you choose which group of users is allowed to promote themselves as global watchers (to avoid having everybody watching everything and though generating too much bugmail).

Ideally, that's something I would like to see implemented in 3.2.

Comment 1

[Max Kanat-Alexander]

The product/component part of this request is a duplicate of Bug 278455.

But yeah, people should probably be able to mark themselves global watchers instead of it being a parameter.

Comment 2

[Frédéric Buclin]

At some point, this bug will probably recude to "remove the globalwatchers parameter".

Comment 3

[Frédéric Buclin]

(In reply to comment #2)
> At some point, this bug will probably recude to

recude -> reduce itself

Comment 5

[Max Kanat-Alexander]

Bugzilla 3.2 is now frozen. Only enhancements blocking 3.2 or specifically approved for 3.2 may be checked in to the 3.2 branch. If you would like to nominate your enhancement for Bugzilla 3.2, set the "blocking3.2" flag to "?", and either the target milestone will be changed back, or the blocking3.2 flag will be granted, if we will accept this enhancement for Bugzilla 3.2.

Comment 6

[Frédéric Buclin]

We are going to branch for Bugzilla 4.4 next week and this bug is either too invasive to be accepted for 4.4 at this point or shows no recent activity. The target milestone is reset and will be set again *only* when a patch is attached and approved.

I ask the assignee to reassign the bug to the default assignee if you don't plan to work on this bug in the near future, to make it clearer which bugs should be fixed by someone else.