Wikimedia Bugzilla is closed!

https://rt.wikimedia.org/Ticket/Display.html?id=3029

http://lists.wikimedia.org/pipermail/wikitech-l/2012-May/060624.html

http://lists.wikimedia.org/pipermail/wikitech-l/2012-May/060793.html

*** Bug 36457 has been marked as a duplicate of this bug. ***

Reset assignee per bug 37789

http://bzr.mozilla.org/bugzilla/extensions/ doesn't list it, as it's only available for bmo itself at http://bzr.mozilla.org/bmo/4.2/files/head:/extensions/ComponentWatching/ . Not sure how bmo specific it is.

I've copied http://bzr.mozilla.org/bmo/4.2/files/head:/extensions/ComponentWatching/ into a local 4.2.4 installation and it seems to work.
It creates a "Component Watching" tab on userprefs.cgi.
This would make the cumbersome "ask an admin to put you into the default CC you of component X" mood.

(In reply to comment #5)
> I've copied
> http://bzr.mozilla.org/bmo/4.2/files/head:/extensions/ComponentWatching/ into a
> local 4.2.4 installation and it seems to work.
> It creates a "Component Watching" tab on userprefs.cgi.
> This would make the cumbersome "ask an admin to put you into the default CC you
> of component X" mood.

Aside from making that moot, it would also make it a lot easier to disable later (by not being stuck on CC for all bugs created before disabling it), assuming it doesn't use CC underneath.

In short:
0) bzr co bzr://bzr.mozilla.org/bmo/4.2 bugzilla-bmo42
1) cd bugzilla-bmo42/
2) make extensions/ComponentWatching/template/en/default/hook/account/prefs/prefs-tabs.html.tmpl:11 say
   "label => "Component Watching (beta)","
   instead of
   "label => "Component Watching","
3) cp /extensions/ComponentWatching/ root@kaulen:/srv/org/wikimedia/bugzilla/extensions/
4) /srv/org/wikimedia/bugzilla/checksetup.pl
5) Profit!

Kaulen needs bzr installing first ;)

Played with ComponentWatching in a local Bugzilla this morning, dropping some stuff for better understanding:

* https://bugzilla.mozilla.org/show_bug.cgi?id=652400 introduced a new (fifth) column which would appear under https://bugzilla.gnome.org/userprefs.cgi?tab=email just called "Component". For me it was empty by default, so if we install this extension we'd have to document this.

* https://bugzilla.mozilla.org/show_bug.cgi?id=684701 added another field to component preferences which would appear under https://bugzilla.wikimedia.org/editcomponents.cgi?action=edit&product=FOO&component=BAR , see https://bug684701.bugzilla.mozilla.org/attachment.cgi?id=598151

Note that this extension is not upstreamed (it's bugzilla.mozilla.org only!).
Plus I still need to play a bit more with it to check that it completely respects rights (e.g. watching Bugzilla components with access restricted via group permissions).

Long term: Need to push Mozilla into upstreaming their bmo extension. That's https://bugzilla.mozilla.org/show_bug.cgi?id=76794

Tried to deploy bzr://bzr.mozilla.org/bmo/4.2/extensions/ComponentWatching/ on boogs.wmflabs.org, but running checksetup.pl triggers:

Adding new column 'watch_user' to the 'components' table...
Adding foreign key: component_watch.product_id -> products.id...
Adding foreign key: component_watch.component_id -> components.id...
Adding foreign key: component_watch.user_id -> profiles.userid...
Adding foreign key: components.watch_user -> profiles.userid...
DBD::mysql::db do failed: Can't create table 'bugs.#sql-3c5_85' (errno: 121) [for Statement "ALTER TABLE components ADD 
     CONSTRAINT fk_components_watch_user_profiles_userid FOREIGN KEY (watch_user)
     REFERENCES profiles(userid)
      ON UPDATE CASCADE ON DELETE SET NULL"] at Bugzilla/DB.pm line 654
	Bugzilla::DB::bz_add_fks('Bugzilla::DB::Mysql=HASH(0x23c5e20)', 'components', 'HASH(0x56be2d0)', 'HASH(0x7fda5e0)') called at Bugzilla/DB.pm line 561
	Bugzilla::DB::bz_setup_foreign_keys('Bugzilla::DB::Mysql=HASH(0x23c5e20)') called at Bugzilla/Install/DB.pm line 685
	Bugzilla::Install::DB::update_table_definitions('HASH(0x16c5bc0)') called at ./checksetup.pl line 199


Would love to check the "components" table for the "watch_user" column in the "bugs" database (to see where this is coming from), and to be on the safe side also run
 SELECT constraint_name, table_name FROM information_schema.table_constraints
 WHERE constraint_type = 'FOREIGN KEY' AND table_schema = DATABASE() ORDER BY
 constraint_name;
but
 mysql> SHOW DATABASES;
 +--------------------+
 | Database           |
 +--------------------+
 | information_schema |
 | test               |
 +--------------------+
 2 rows in set (0.00 sec)
seems to not offer me the bugs database (and cannot log in as root).