Custom Query (332 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (184 - 186 of 332)

Ticket Resolution Summary Owner Reporter
#156 fixed Can't change comments created with email2trac bas Chris.Nelson@…
Description

We use the Ticket Change plugin but find that comments added by email2trac are not editable. Clicking the Change button leads to

Change Ticket Comments Ticket change '8' not found. Please try again.

Perhaps email2trac isn't filling in all the tables or fields Ticket Change expects.

#157 fixed workflow option is ignored (patch) bas thomas.moschny@…
Description

In order to avoid closed tickets being reopened by email2trac, I configured 'workflow: leave', but that didn't work at first. The following patch was needed.

--- email2trac-1.0.0/email2trac.py.in.orig	2009-09-02 10:57:42.000000000 +0200
+++ email2trac-1.0.0/email2trac.py.in	2009-10-21 15:40:53.000000000 +0200
@@ -660,7 +660,7 @@ class TicketEmailParser(object):
 			#b = controller.get_ticket_changes(req, tkt, 'reopen')
 			#print 'get_ticket_changes :', b
 
-			if self.WORKFLOW and (self.VERSION in ['0.11']) :
+			if self.WORKFLOW and self.VERSION == 0.11:
 				from trac.ticket.default_workflow import ConfigurableTicketWorkflow
 				from trac.test import Mock, MockPerm
 

In the long run, it might be a better idea to turn self.VERSION into a string.

#158 fixed Need Help:Struggling to get Email2Trac working on Debian bas roshan_shankar@…
Description
Hi,
I have Debian with exim4 installed and I am trying to use Email2Trac
to email tickets into Trac.

I have confirmed that emails can be sent and received by the Debian
box - emails to root@mydebainbox.mycompany.com get to it and likewise
emails I send from there get to external email addresses.

I have two projects - a project called test whose email is
test@mydebianbox.mycompany.com and a project called "real" whose email
is real@mydebianbox.mycompany.com

The projects are all under /var/lib/trac - in test and real folder,
respectively.

A few issues I have are

1. I do not know how to configure Email2Trac.conf for multiple
projects. An example would help. I, for now, changed the project
entry's value on the [default] to point to my test project.

2. Per the MTA configuration page, I am not supposed to enter entries
in /etc/aliases but use the router and transport files to set up the
forward to email2trac. The problem is I do not understand router/
transport files well enough. I copied the example on the page and that
did not work.

So, I went ahead and created the aliases in /etc/aliases. And, tested
it from the box using  - mail test < msg.txt and that did create a
ticket on the test project.

Then, I tried to email to test@mydebianbox.mycompany.com and I get a
message after a few hours saying

This message was created automatically by mail delivery software.

A message that you sent has not yet been delivered to one or more of
its recipients after more than 24 hours on the queue on
stastepagl01.dillonkane.com.



The message identifier is:     1N3ui2-0001J3-LH

The date of the message is:    Fri, 30 Oct 2009 11:52:18 -0500

The subject of the message is: test



The address to which the message has not yet been delivered is:



  pipe to |"/usr/bin/email2trac --project=test --ticket_prefix=test"

    generated by test@mydebianbox.mycompany.com



No action is required on your part. Delivery attempts will continue
for some time, and this warning may be repeated at intervals if the
message remains undelivered. Eventually the mail delivery software
will give up, and when that happens, the message will be returned to
you.



Please help me to get the Email2Trac working either using
router/transport or using aliases.



TIA

Roshan
Note: See TracQuery for help on using queries.