-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11.09.2013 23:13, Dimitri Maziuk wrote:
On 09/11/2013 01:10 PM, Steffen Hoffmann wrote:
On 11.09.2013 16:30, Dimitri Maziuk wrote:
I believe the other piece of the puzzle is the ability to update
/etc/trac/aliases (or whereever we put the
On 12 sep. 2013, at 09:00, Steffen Hoffmann hoff...@web.de wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11.09.2013 23:13, Dimitri Maziuk wrote:
On 09/11/2013 01:10 PM, Steffen Hoffmann wrote:
On 11.09.2013 16:30, Dimitri Maziuk wrote:
I believe the other piece of the puzzle is
Or one could have one email address per ticket,
like in Debian (e.g. 123...@bugs.myserver.com).
+1. This is the interface people who use such tools come to expect.
3. There is no reply possible from within Trac. This is something
OpenERP does very nicely. One can handle the
On 2013-09-11 05:51, Bas van der Vlies wrote:
I am just back from vacation and read this email2trac thread.
Message-id's are not stored in the trac database and if you submit a
ticket via the web interface there is no knowledge about the message id.
what we want is a flexible reply to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11.09.2013 16:30, Dimitri Maziuk wrote:
I believe the other piece of the puzzle is the ability to update
/etc/trac/aliases (or whereever we put the aliases file) and run
'newalias' when a new ticket is created. And the question of whether to
On 09/11/2013 01:10 PM, Steffen Hoffmann wrote:
On 11.09.2013 16:30, Dimitri Maziuk wrote:
I believe the other piece of the puzzle is the ability to update
/etc/trac/aliases (or whereever we put the aliases file) and run
'newalias' when a new ticket is created. And the question of whether to
Quoting Dimitri Maziuk dmaz...@bmrb.wisc.edu:
or forget if it was '#number' or 'number' or what and pick the wrong one...
In fact, it is '#number:' - how often did I forget the trailing colon?
Message IDs don't work. For instance the version of thunderbird I'm
writing this in has reply to
We are looking at using email2trac to allow users to add and modify tickets. I
am curious what experience people have had with this. Not so much how
email2trac works, but how you have managed getting users to format messages
correctly.
I think we are mainly looking at letting users create
We have been running trac + email2trac successfully for a while
here. The major issues we've run into are:
Mail loops, make sure you double and triple check your black
lists because if you don't you'll wind up with enormous trac
crippling tickets and DoS
On 9/4/13, W. Martin Borgert deba...@debian.org wrote:
Quoting roger.oberholt...@gmail.com:
We are looking at using email2trac to allow users to add and modify
tickets. I
am curious what experience people have had with this. Not so much how
email2trac works, but how you have managed getting
Quoting roger.oberholt...@gmail.com:
We are looking at using email2trac to allow users to add and modify
tickets. I
am curious what experience people have had with this. Not so much how
email2trac works, but how you have managed getting users to format messages
correctly.
No guidelines, just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04.09.2013 17:07, Garrett McGrath wrote:
I like it for a basic setup but our ultimate goal is to split ticket
handling out to RT and keep trac as our KB system for our labs due to
needing some features that trac can't support.
-Garrett
You're
Steffen,
Fundamentally we've just out grown trac's ticket handling for what we
were using it for. We aren't using trac for project management (in this
case) we are using it as a knowledge portal and helpdesk system for our
Institutes labs. We've grown since we set this up from around 25
On 09/04/2013 09:52 AM, W. Martin Borgert wrote:
1. Users tend to forget the ticket number in the subject or they
even remove it. This leads to creation of duplicates. There is
no easy merging of tickets in Trac, so this means work :~(
or forget if it was '#number' or 'number' or
14 matches
Mail list logo
