Bug mails should explain why the person is getting emailed.
Bug #3797 reported by
Jorge Bernal
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Christian Reis |
Bug Description
I often receive bug mails (I guess they are for motu or gnome), but they have my address as recipient, instead of a team name. So most of the times I don't know why I'm receiving that mail.
The equivalent for specification tracking is bug 39420.
Changed in malone: | |
status: | New → NeedInfo |
description: | updated |
Changed in malone: | |
status: | Needs Info → Confirmed |
description: | updated |
Changed in malone: | |
assignee: | bjornt → kiko |
status: | Confirmed → In Progress |
Changed in malone: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
We need to strike a balance here between an informative, useful piece of mail, and one that isn't littered with too much information that would clutter up the messages of people who reply by email. Repeating product or package names in the bugmail notifications has the risk of such cluttering, I think.
But, I've started to make some headway on making bugmail more useful.
One is that I've added a footer. Here's an example:
To: <email address hidden>
From: Foo Bar <email address hidden>
Subject: [Bug 9] Firefox crashes all the time
Date: Mon, 28 Nov 2005 20:01:27 -0000
Public bug report changed: 192.168. 1.2:8086/ malone/ bugs/9
http://
Comment:
Yes, I agree, firefox does crash a lot.
--
You are receiving this message because you are on the Cc list of this bug,
or are a member of a team that is, or you are assigned to fix it.
Another thing that I think might help is if, via the web UI, you could reply to an individual message like in Bugzilla. That, in combination with the subject of the message, would, IMHO, help give a lot of useful context without cluttering up the message.
(I believe the reason we don't already allow replying to individual comments in the web UI might be to not encourage too much discussion on a bug, due to the risk of flame wars, etc. In practice though, not being able to reply to an individual comment is just a pain in the ass, IMHO. :)
What do you think about these suggestions Jorge?