Feature #3660
openConfigurable subject of notification email for issue_add/issue_edit
0%
Description
Since Gmail is grouping emails into chains by their subject, it's very preferred that email subject will stay the same during all life of issue.
I.e., in /app/models/mailer.rb
, in both issue_add()
and issue_edit()
email subject should not rely on issue status. I'm using:
subject "[#{issue.project.name} - #{issue.tracker.name} ##{issue.id}] #{issue.subject}"
Of course, it should be configurable per-user (something like checkbox "Gmail-friendly subjects" in email settings)
Related issues
Updated by Burt Culver about 15 years ago
+1 - this would be great to be user configurable. Right now messages about tickets go all over the place in my gmail.
Updated by Burt Culver about 15 years ago
Another option would be to set the In-Reply-To email header field with a consistent message ID. This may cause gmail to thread the issues even with different subject lines.
Updated by David Paleino almost 15 years ago
It would be really nice if this was implemented by keeping the Message-ID of the first mail (i.e. when the bug is opened), and using that with In-Reply-To and References in subsequent e-mails.
Also, it would be cool to organize comments as a real mail-thread, i.e. each with a Message-Id used by subsequent comments (maybe also adding a "Reply" link to the comments view?)
David
Updated by Ling Li almost 12 years ago
Updated by Toshi MARUYAMA over 10 years ago
- Related to Feature #13111: New setting to include the status changes in issue mail notifications subject added
Updated by dumb blob over 9 years ago
+1
I'm as well raising my hand for having customizable subjects.
Updated by Marius BÄ‚LTEANU almost 6 years ago
I've added a patch to #13111 that gives you the option to include or not the status changes in issue mail notifications subject.
Updated by Don Pedro almost 6 years ago
Marius BALTEANU wrote:
I've added a patch to #13111 that gives you the option to include or not the status changes in issue mail notifications subject.
Thank you very much, Marius. It's nice to see that even 9 years old bugs are addressed eventually. Just too bad I'm no longer using Redmine :(