This is really important in my opinion. Currently it is not really possible to follow an issue by notification emails. In Gmail e. g. the Mails to one Ticket from the same sender are grouped together, but from different senders it is different Threads, so the messages are out of order because of the missing In-Reply-To/References headers and thus you do not read the messages in the correct order.
--- ** [tickets:#6328] Use In-Reply-To: and References: headers for outgoing ticket emails** **Status:** open **Created:** Tue Jun 04, 2013 02:04 PM UTC by Hanspeter Niederstrasser **Last Updated:** Mon Jul 08, 2013 04:30 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.
