Comment 0 for bug 194647
Revision history for this message
| Scott Kitterman (kitterman) wrote Launchpad sends me multiple mails about bugs when I assign them to myself | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
I review Bug 144490 and decide I might be able to fix it.
I assign myself the bug and make a comment that I'm going to try and fix it.
To my suprise I get bug mail that seems wrong in many ways.
First, I get a copy of the original bug that screams [NEW] in the subject line. This is wrong. The bug is not new. It's 5 months old. It's also shouting at me.
This bugmail wrongly says:
You have been subscribed to a public bug:
I haven't. I have assigned myself to a public bug. I know this because I did it and LP knows it was me that did it. There's no need to tell me what I already know.
I have to scroll all the way down to the bottom of the message to discover that I'm assigned this bug (which I already know in this case).
Then I get a second mail that include the (redundant) information that I"m assigned the bug (which I already know because I did it and because the first bugmail says the same thing) and also includes the comments that I left.
1. There is no reason to send me a copy of the bug. I didn't ask for it. I don't want it. I'm pretty sure I didn't get it before (I get pleny of bugmail as it is).
2. Please don't shout at me. [NEW] is really overkill. If you want people to be able to key off of the first mail they get for a bug, stuff it in an x-header in the message. There's no need to be in my face about it.
3. Please don't send me two mails at the same time. Bundle it up into one mail.