Custom Query (332 matches)
Results (142 - 144 of 332)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#100 | fixed | problems with ticket follow-up | bas | zygis@… |
Description |
im having problems posting follow-ups to tickets from emails. email2trac works to create new tickets from email, so i dont think there's a problem there, however the follow-ups just never appear. any ideas where i can look for more clues? email2trac is working with fetchmail on a single project. here's my email2trac.conf [DEFAULT] project: /d/trac/darqenv debug: 2 umask: 022 reply_all : 1 mailto_link: 0 email_comment: > email_header: 0 trac_version: 0.11 enable_syslog : 1 alternate_notify_template: 0 verbatim_format: 0 strip_signature: 1 use_textwrap: 70 ticket_update: 1 output of fetchmail fetchmail: 1 message for trac@example.com at mail.example.com. .TD: saving email to /tmp/msg.txt TD: part1: Content-Type: text/plain TD: part1: filename: None TD: this part is not multipart TD: writing part1 (/tmp/part1) TD: saving email to /tmp/tmpEuThG_.email2trac fetchmail: reading message trac@example.com@mail.example.com:1 of 1 (1392 header octets) (149 body octets) flushed read:errno=0 |
|||
#101 | fixed | Correctly set custom field default values when creating a ticket | bas | ben@… |
Description |
Currently, all ticket custom fields are set to None instead of their proper default values when a ticket is created by email2trac. The patch below fixes the problem --- email2trac.py.in.txt (saved version) +++ (current document) @@ -682,7 +682,13 @@ # default trac value # - value = self.get_config('ticket', 'default_%s' %(name) ) + if not field.get('custom'): + value = self.get_config('ticket', 'default_%s' %(name) ) + else: + value = field.get('value') + options = field.get('options') + if value and options and value not in options: + value = options[int(value)] if self.DEBUG > 10: print 'trac.ini name %s = %s' %(name, value) |
|||
#102 | fixed | Can't update tickets from an email | bas | tim@… |
Description |
When I reply to a ticket and follow the conventions outlined in the documentation, the ticket does not update (either using commands in the subject or text in the body of the email). I see the following dump in my log: Nov 16 01:19:28 wilsonserver email2trac: TypeError?: unsupported operand type(s) for -: 'int' and 'datetime.datetime' Nov 16 01:19:28 wilsonserver email2trac: Traceback (most recent call last): Nov 16 01:19:28 wilsonserver email2trac: File "/usr/local/bin/email2trac", line 1284, in <module> tktparser.parse(sys.stdin) Nov 16 01:19:28 wilsonserver email2trac: File "/usr/local/bin/email2trac", line 845, in parse if self.ticket_update(m, spam_msg): Nov 16 01:19:28 wilsonserver email2trac: File "/usr/local/bin/email2trac", line 647, in ticket_update tkt.save_changes(self.author, body_text, when) Nov 16 01:19:28 wilsonserver email2trac: File "/usr/lib/python2.5/site-packages/Trac-0.11.2-py2.5.egg/trac/ticket/model.py", line 230, in save_changes when_ts = to_timestamp(when) Nov 16 01:19:28 wilsonserver email2trac: File "/usr/lib/python2.5/site-packages/Trac-0.11.2-py2.5.egg/trac/util/datefmt.py", line 56, in to_timestamp diff = dt - _epoc Nov 16 01:19:28 wilsonserver email2trac: TypeError?: unsupported operand type(s) for -: 'int' and 'datetime.datetime' I am using Trac 0.11.2, Fedora 7, Apache 2.2.7-1, Python 2.5-15 and email2trac-0.40 |