On 09/04/2013 09:52 AM, W. Martin Borgert wrote: > 1. Users tend to forget the ticket number in the subject or they > even remove it. This leads to creation of duplicates. There is > no easy merging of tickets in Trac, so this means work :~(
or forget if it was '#number' or '&number' or what and pick the wrong one... > Possible improvements: email2trac should work on base of > message-ids in the e-mail header instead of parsing the subject > like OpenERP. Message IDs don't work. For instance the version of thunderbird I'm writing this in has "reply to list" but not "new message to mailing list". So people often hit "reply to list" to start a new thread. Then you have message ID for one thread and subject for another -- now think "thread" == "ticket". > Or one could have one email address per ticket, > like in Debian (e.g. [email protected]). +1. This is the interface people who use such tools come to expect. > 3. There is no reply possible from within Trac. This is something > OpenERP does very nicely. One can handle the ticket completely in > the web application, while in Trac you have to go back to your MUA. That could be handy but trac can already e-mail ticket updates. I think integrating that with email2trac replies might be worth looking into instead: e.g. someone e-mails a ticket update, they automagically get on cc list. > 4. Spam was an issue for us, but we probably did not investigate > enough what to do about it. Well, if you have #1 you'll probably have to run your own smtpd anyway, that's where you can add spamassassin and/or whatever. -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu
signature.asc
Description: OpenPGP digital signature
