Sorting out upstream and project bugtrackers

[Christian Robottom Reis]

I had a call with Bjorn today to define how our handling of bugtrackers
could be improved, as part of his work in improving forwarding of bugs
to upstream. The current system allows you to register a standalone
bugtracker, and it also allows you to register a bugtracker associated
with a project, and there is no way of changing that association after
creation -- which is a wart! There is also now way of specifying that a
certain product uses a bugtracker, which means we can't direct the user
to a specific bugtracker when he wants to add a new watch -- we end up
with that sucky drop-down listing all registered bugtrackers.

Relevant bugs:

    https://launchpad.net/products/malone/+bug/1737
    https://launchpad.net/products/malone/+bug/2879
    https://launchpad.net/products/malone/+bug/4592
    https://launchpad.net/products/malone/+bug/33481
    https://launchpad.net/products/malone/+bug/35728
    https://launchpad.net/products/malone/+bug/42480
    https://launchpad.net/products/malone/+bug/49818

The discussion we had proposes doing the following:

    - Having all registering of bugtrackers be done standalone, under
      /bugtrackers.

    - Allowing an existing bugtracker to be attached to a project, which
      would serve as the default bugtracker for all its products. This
      would be a simple drop-down in the project's edit form.

    - Allowing an existing bugtracker to be attached to a product, which
      would act as an override to the product's project's bugtracker
      (yeah, read that again <wink>).

      This would the product to select between three different options:

        ( ) This product uses Malone officially
        (*) This product uses [ Ping dynasty Bugzilla | v] 
        ( ) This product doesn't use a bugtracker 

      And, if the product had a project related to it, the last option would
      read something like:

        ( ) This product uses the GNOME Project Bugzilla
            (defined in the GNOME Project)

This should make the bugtracker creation process clearer, and will allow
us to really improve the way adding new bug watches is done.

Have an opinion? Let me know! Thanks,
-- 
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3376 0125