Custom Query (332 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (136 - 138 of 332)

Ticket Resolution Summary Owner Reporter
#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"?

#143 wontfix Creating a new ticket via email bas cbidwell@…
Description

Hi, I can't seem to get this working. Replies to tickets work fine, but creating a new ticket...Not working.

Here is my email2trac.conf:

[trac] project : /home/svn/projects/trac debug : 0 enable_syslog: 1 spam_level : 0 reply_all : 1 umask : 022 mailto_link : 1 mailto_cc : user@… ticket_update: 1 trac_version : 0.11

And here is my /etc/aliases statement: trac: |"/usr/local/bin/run_email2trac --project=trac --ticket_prefix=trac"

#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.

Note: See TracQuery for help on using queries.