Issue 1036860
Created on 2004-09-29 08:19 by hgibson50, last changed 2004-09-29 08:19 by hgibson50.
msg3351 |
Author: [hidden] (hgibson50) |
Date: 2004-09-29 08:19 |
|
I am monitoring a number of bugs entered into Roundup.
At the moment all the emails I receive are not sorted in
any way - it's just the order in which they were received.
It would be much nicer if the first email for a new issue
had a message ID which was stored with the issue.
Subsequent emails could then have a "In-reply-to" field
which included that message ID.
Then my email client would thread the messages
correctly and keep information related to a particular
issue together.
Hugh Gibson
|
msg3352 |
Author: [hidden] (richard) |
Date: 2004-09-29 08:34 |
|
Logged In: YES
user_id=6405
Roundup already does this.
|
msg3353 |
Author: [hidden] (hgibson50) |
Date: 2004-09-29 10:51 |
|
Logged In: YES
user_id=732318
As far as I can see looking in the source code, it does this for
issues submitted via email. However, for issues submitted via
the web it doesn't. In other words, if someone creates an
issue via the web interface, and subsequently comments to it
via the web interface, the second email sent out to the nosy
list doesn't have any "in-reply-to" field. Searching
for "inreplyto" in the source code shows that it is only setup
when receiving email submissions of bugs.
I tried modifying send_message in roundupdb.py, adding
another line after:
223: if msgid is not None:
224: messages.set(msgid, messageid=messageid)
as:
224a: messages.set(msgid, inreplyto=messageid)
The idea being that if the message had been put in by the
web, it would then have the inreplyto field set up when
creating the original notification message for the issue.
However, this hasn't worked and as I've had to do it by
asking the system administrator (my boss) to hand edit, I'm
not happy to do much more experimenting.
Any ideas why that didn't work? Any other guidance?
Hugh
|
|
Date |
User |
Action |
Args |
2004-09-29 08:19:52 | hgibson50 | create | |
|