can't stop getting bug spam for bug 114605

[Robert Collins]

 affects launchpad

So, bug 114605, which is a dup of 205887, was in the distant past set as
a task on baz1x, which was wrong. It was marked invalid there, and a new
task set on network-manager (correctly). However, changes to the bug
result in mail the baz1x maintainers.

Several UI issues cropped up recently with this. I'll get into them in a
second, but for now, to stop getting mails, I've made the baz1x task
into a malone task; that way the malone devs get the mails :).

issues:
 - couldn't change the task on bug 114605 while it was a dup of 205887,
which only matters because the mail system notifies based on *both* bug
205887's details and bug 114605's details. If we use data from a bug to
change system behaviour, users need to be able to change the bug to
garden that data.
 - bug mail was being sent through the bug's duplicates details; this is
not obvious to users, bug 151101 talks about this
 - there is no way to delete (as opposed to marking invalid) the
relationship with 'baz1x' which was _never_ relevant for the bug. I
suggest there is a difference between 'we considered X and its not
relevant for this bug' and 'someone added a task by mistake'. The latter
is the case here.

-Rob

--
GPG key available at: <http://www.robertcollins.net/keys.txt>.

[Diogo Matsubara (matsubara)]

Hi Robert, you've reported a couple of bugs so I'm marking this one as duplicate of another bug.

The main problem reported seems to come from the fact that you couldn't unsubscribe the implicit subscriber from bug 114605. The implicit subscriber in this case is the project registrant (~baz-developers). This is bug 204980

The other issue is that you couldn't edit the duplicate bug. This is the resulting implementation of bug 54801 and discussed in bug 137408.

The fact that you can't delete a bugtask is bug 1342.