incubator-allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Brondsema" <brond...@users.sf.net>
Subject [allura:tickets] #6328 Use In-Reply-To: and References: headers for outgoing ticket emails
Date Mon, 28 Oct 2013 17:50:14 GMT
This is working great in my opinion, except for a case of nested replies so I'm going to re-open
it for that:

If I hit "reply" on a comment and make a nested reply, the email has References and In-Reply-To
headers that properly match the parent email.  However, in Thunderbird, the message doesn't
get included in that thread, it makes a new thread.  I suggest reading up on how those headers
should be, but IIRC one of the headers can have multiple values and we may need to include
the original id in addition to the parent (and may even all intermediate message ids if you're
in a very deep nested discussion)


---

** [tickets:#6328] Use In-Reply-To: and References: headers for outgoing ticket emails**

**Status:** in-progress
**Labels:** 42cc 
**Created:** Tue Jun 04, 2013 02:04 PM UTC by Hanspeter Niederstrasser
**Last Updated:** Thu Oct 24, 2013 08:16 PM UTC
**Owner:** nobody

Outgoing ticket emails should use the In-Reply-To: and References: headers so that recipient
user agents can group messages from the same ticket together.

For example, e-mails from Canonical's Launchpad tracker use the Message-ID of the original
post in the References: field of follow up posts.  The same should happen with SF ticket e-mails.
 In case a user replies via e-mail or using the "Reply" button on the web interface, the Message-ID
of the 'parent' message should be appended to the In-Reply-To: and References: headers.


---

Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options.
 Or, if this is a mailing list, you can unsubscribe from the mailing list.
Mime
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message