Hi I think the subject field should stay the same troughout the bugs life-cycle today we have: (as far as I recall) [bug <number>] new - <summary> [bug <number>] changed - <summary> [bug <number>] fiex - <summary> but this screws up threading. resulting in a thread for each subject, thats at least 3 thread per bug If the bugs had the same subject throughout the lifecycle like [bug <number>] <summary> threading would group mails on a per bug basis, resulting in only one thread per bug. cheers from denmark Henrik Lynggaard

If your only concern is threading, perhaps you'll like bug 31314 better.

The proposal in bug 31314 would really be the better solution. Henrik (or anyone else), please reopen this bug if you disagree. *** This bug has been marked as a duplicate of 31314 ***

While bug 31314 is a more elegant solution, do we know if that will solve the sorting problem for most e-mail clients? How about we mark this as being blocked by 31314, and if it turns out that 31314 fixes the problem for everyone then we can close this one as well.

This is not a duplicate. It's an alternative solution to the same problem. Both bugs should stay open until we decide which one (or both?) we're doing, at which point the other can get closed WONTFIX.

Adding dependency then ... sorry for the confusion.

-> Bugzilla product, Email component, reassigning.

And what if the summary changes?

Really, the other bug should solve the problem for everyone. If your client doesn't support basic reply-to threading, you really need to be thinking about upgrading to a client written since 1994. And as pointed out this solution completely fails to deal with the (frequent) case in which a bug is re-titled to reflect a new reality. My personal suggestion is that this is WONTFIX.

Changing default owner of Email Notifications component to JayPee, a.k.a. J. Paul Reed (preed@sigkill.com). Jake will be offline for a few months.

(In reply to comment #4) > This is not a duplicate. It's an alternative solution to the same problem. > Both bugs should stay open until we decide which one (or both?) we're doing, > at which point the other can get closed WONTFIX. Bug 31314 has landed, and will be shipped with 2.20. As such, in accordance with this comment from Dave, I'm marking this bug as WONTFIX.

clearing target of DUPLICATE/WONTFIX/INVALID/WORKSFORME so they'll show up as untriaged if they get reopened.