Open
Bug 1421024
Opened 8 years ago
Updated 2 years ago
Consider changing site default for "Add 'New:' to subject line of email sent when a new bug is filed"
Categories
(bugzilla.mozilla.org :: Email Notifications, enhancement)
Tracking
()
NEW
People
(Reporter: gps, Unassigned)
Details
Attachments
(1 obsolete file)
GMail doesn't fully respect In-Reply-To and References email headers and messages with different subjects appear in different GMail threads.
Mozilla's corporate email is provided by GMail.
By default, Bugzilla prefixes bugmail for new bugs with "New: ". This means that GMail renders the "New: " bugmail in a different thread from all replies.
Having to reconcile multiple GMail threads for the same bugs wastes a lot of time. For example, when I'm triaging my bugmail and come across a "New: " message without the context of the replies, I'm unsure of the state of the bug. I often read the bug report in detail then open the bug to reply - only to find out that the bug has already been acted on and is fixed! I waste precious time paging in the contents of the initial bug report because the bug updates aren't rendered in the same GMail thread. I reckon this issue wastes 10+ hours of my time per year.
TIL Bugzilla has an "Add 'New:' to subject line of email sent when a new bug is filed" setting under "General Preferences." The site default for bugzilla.mozilla.org is "On." Switching this to "Off" fixes the GMail threading issue!
Given that Mozilla's corporate email is GMail and the current site default of this feature is sub-optimal for GMail users, I think we should change the site default to "Off." Alternatively, perhaps we could change the default for known-GMail domains (like mozilla.com and gmail.com).
| Reporter | ||
Comment 1•8 years ago
|
||
I also filed bug 1421042 to request a "unified subject for all bugmail" feature.
Updated•7 years ago
|
Type: defect → enhancement
Comment 3•2 years ago
|
||
The content of attachment 9381537 [details] has been deleted for the following reason:
Spam
You need to log in
before you can comment on or make changes to this bug.
Description
•