Custom Query (332 matches)
Results (250 - 252 of 332)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#212 | fixed | same error as in [428] | bas | adam.lucke@… |
Description |
as in [428] used set.logger.error(...) instead of self.logger.error(...) in source:trunk/email2trac.py.in@428#L2067 |
|||
#253 | fixed | Script easily confused by duplicate subject lines | bas | kofal002@… |
Description |
As mentioned in #252, we're using this script to handle incoming customer email. In this use case, it is possible to confuse the script simply by having two tickets named the same (or, with Email2Trac, two emails with the same subject line). To reproduce:
Expected behavior:
|
|||
#343 | fixed | Sender is not notified when new ticket is created | bas | leonardo.ascenso@… |
Description |
Today I made an upgrade to the last version. I don't upgrade email2trac for YEARS! Now senders are not notified on new ticket/ticket update. I have this error on my log and I think that's why sender is not notified by email. 2014-07-17 18:52:28,574 email2trac lefatech.trac: function unique_attachment_names() 2014-07-17 18:52:28,574 email2trac lefatech.trac: function get_body_text() 2014-07-17 18:52:28,716 email2trac lefatech.trac: function attach_attachments() 2014-07-17 18:52:28,716 email2trac lefatech.trac: function mail_workflow: 2014-07-17 18:52:28,717 email2trac lefatech.trac: function notify() 2014-07-17 18:52:28,754 email2trac lefatech.trac: Failure sending notification on creation of ticket #10060: [Errno -2] Name or service not known It seems an error on email2trac line 2922 (tn.notify(tkt, new, modtime)) I'm I doing something wrong? |