Bug mails should be threadable

Bug #181 reported by Thom May on 2005-02-25
6
Affects Status Importance Assigned to Milestone
Launchpad itself
Medium
Björn Tillenius

Bug Description

We had originally decided to store the message id of the initial notification email, but I think your idea of generating the message id based on the message id is better.

We will support full threading once we have the email interface implemented, but the method you scetch out seems a good solution until then.

Thom May (thombot) wrote :

I just implemented this in Ubuntu bugzilla, if you want to look at the bug mail it sends.

Stuart Bishop (stub) wrote :

We had originally decided to store the message id of the initial notification email, but I think your idea of generating the message id based on the message id is better.

We will support full threading once we have the email interface implemented, but the method you scetch out seems a good solution until then.

Luis Villa (luis-villa) wrote :

Two notes:
* this is critical for high-volume bug handlers, to be able to select a 'thread' (aka all comments in a bug which you've later read on the web, or otherwise decided you don't care about) and then delete/mark read.

* There is extensive discussion on the 'ideal' threading algorithm (given bug ids and comment ids) here:
https://bugzilla.mozilla.org/show_bug.cgi?id=31314

Thom May (thombot) wrote :

threading correctly for replies to comments would be great in the long run, but threading is absolutely critical to the usefulness of emails a BTS sends out, as Luis correctly states.
Will this be in 1.0?

Changed in malone:
assignee: nobody → bjornt
status: New → Accepted
Björn Tillenius (bjornt) wrote :

Yes, emails that get sent out will be threadable in 1.0

Changed in malone:
status: Accepted → Fixed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers