Custom Query (332 matches)
Results (109 - 111 of 332)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#139 | fixed | Configure more projects in email2trac.conf | bas | didley@… |
Description |
Dear all, I'm using email2trac version 0.80. All works fine and I'm happy to have this small program with this big effect. Just one thing. The configfile email2trac.conf has the possibility to add another project. Your description says: project : /data/trac/jouvin # use -p|--project jouvin Please what means use -p or --project my second project ends in [BlaProject] project: D:\Project\BlaProject but it works not. How I have to use -p or --project? |
|||
#142 | fixed | Some fields are no longer available using alternate_notify_template | bas | hju@… |
Description |
In our old environment (email2trac 0.30 / trunk 218) we are using the alternate_notify_template to inform the reporter about acceptance of the ticket. In the mail-body we use the following text (example): Hello, your request was insertet as $ticket.id in our system. Your request was: $ticket.description ... Everything works fine! Now we have established a new environment under windows with email2trac 0.80 and python 2.5. Problem: The $ticket.description is displayed, but $ticket.id is empty. In the Mail-Header, the ID ist displayed! Taking a close look shows: with the "old" email2trac, if a ticket was created there was "change-entry" for each ticket: *id set to 411 this is now missing. Is it possible, that the ID is no longer known due to this missing "update"? |
|||
#144 | fixed | Better Unicode support | bas | trumbitta@… |
Description |
When a non-ASCII character is in the description, the message will not be parsed and the script will exit. I'll try to fix this figuring out where to put a .encode('utf-8') but I'm not a python programmer... I guess this is a problem wich not only affects the description, but also other fields. You can easily check by adding an è somewhere in the description of a ticket. |