Unassigning yourself from a duplicate bug report

Asked by Brian Murray

With the latest update to Launchpad it does not seem possible to modify bug reports that are marked as a duplicate of another bug report because it is no longer possible to click on the importance or status. So if I want to unassign myself from a bug report, as it has been marked as a duplicate of another bug and I no longer want to receive e-mails about either bug, I have to do some url hacking (by adding /+editstatus) to unassign myself. Is that right or am I missing the new place to click on the bug report?

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Christian Reis (kiko) said :
#1

On Mon, Aug 27, 2007 at 02:08:05PM -0000, Brian Murray wrote:
> status. So if I want to unassign myself from a bug report, as it has
> been marked as a duplicate of another bug and I no longer want to
> receive e-mails about either bug, I have to do some url hacking (by

We don't notify assignees of duplicate bugs, last I checked. Are you
sure this is the case?
--
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3376 0125

Revision history for this message
Brian Murray (brian-murray) said :
#2

I have already deleted the e-mail but I believe I received it from bug https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/134206 . Looking at the activity log and my procmail log it looks like there were some comments after the bug was marked as a duplicate which I received the e-mail for. Here is the snippet from my procmail log if that will help:

From <email address hidden> Sat Aug 25 01:03:01 2007
 Subject: [Bug 134206] Re: alsa hda-intel not working anymore
From <email address hidden> Sat Aug 25 01:32:55 2007
 Subject: Re: [Bug 134206] Re: alsa hda-intel not working anymore

Doesn't the "From <email address hidden>" indicate that I was direct recipient of the e-mail?

Revision history for this message
Christian Reis (kiko) said :
#3

It doesn't indicate you were a direct subscriber of the bug; it just indicates that Launchpad sent you the email directly (and not via a mailing list). So it doesn't rule out you being indirectly subscribed through some means.

However, the code that gathers duplicate notifications sure implies it's not including indirect subscribers from dupes. Are you sure there is no other means you might have been receiving the email at the time? It would really help to have the evidence on-file (which is why you should never delete any bugmail -- always archive it!)

Revision history for this message
Brian Murray (brian-murray) said :
#4

Thinking about it more whether or not I received an e-mail isn't really the point. My concern was with not being able to unassign yourself from bug reports that have been marked as duplicates of another.

Revision history for this message
Christian Reis (kiko) said :
#5

On Tue, Aug 28, 2007 at 07:44:05PM -0000, Brian Murray wrote:
> the point. My concern was with not being able to unassign yourself from
> bug reports that have been marked as duplicates of another.

As Matthew asked you before, why is this a problem? Is there any listing
or report that is including the duplicate bug which shouldn't?

Can you help with this problem?

Provide an answer of your own, or ask Brian Murray for more information if necessary.

To post a message you must log in.