Feature #603
closed
Don't include new status for issues in email subject
0%
Description
Ideally, the subject would just contain the project name, the tracker, the issue #, and the subject of the issue. This is useful because it allows email clients to thread all emails relating to a single issue together. This is the behaviour already, except when the status is changed.
Also, of interest, text in the subject enclosed in square brackets is ignored for the purposes of threading, but I wouldn't follow the PHP bug tracker's example of including the information there, for it is in the body anyway. Bugzilla, like we currently do, puts the bug # in square brackets. This is harmless (for we'll never work around subject changes short of including a Reply-To header).
Related issues
Updated by Geoffrey Sneddon almost 16 years ago
- Status changed from New to Resolved
This is really just a dupe of #1401.
Updated by Azamat Hackimov over 14 years ago
- Status changed from Resolved to Closed
Updated by Ling Li almost 12 years ago
I probably should start a new issue, or can someone help to change the status of this issue from "Closed" to "Reopened"?
It seems that #1401 doesn't fix the email grouping problem; at least with Gmail, email notifications from the same issue but with different subjects (the issue status changed) don't group together. I don't know how Gmail groups emails (i.e., how those headers added in #1401 fail with Gmail), but removing the issue status from the email subjects should help.
Can people that use other email clients also suggest if email grouping works for them or not?
Thanks.
Updated by Francewhoa (Francois Carpentier) almost 12 years ago
+1 for this
#1401 doesn't work with Gmail. Reply from Gmail: "A conversation will break off into a new thread if the subject line of the conversation is changed" Source: http://support.google.com/mail/bin/answer.py?hl=en&answer=5900
Same here I would like to re-open this issue. How do we do that?
Updated by Francewhoa (Francois Carpentier) almost 12 years ago
I searched but could not find how to re-open this issue so I created a new one at #13111