Custom Query (332 matches)

It would be useful to get email2trac aware of the 'workflow' entry of trac.ini's [ticket] section.

It would help to trigger custom workflow operations that are not handled by Trac's ConfigurableTicketWorkflow.

It would be nice to have a paired flag for the 'ticket_update' flag that reopens closed tickets when new emails related to those tickets are received. Or alternatively checks to see if the ticket is closed, opening a new ticket instead of appending to the old ticket.

This would be a huge help for our issue tracking system (we don't use trac so much for project management but more for a portal w/ issue tracking).

To whom it may concern:
    I'm looking at modifying the email2trac script to enable it to
handle a 'category' flag.  Specifically we are using Trac as a data
portal for our users and are exploring using the ticket system to
track
help requests to make life easier for our users (quick referrence to
past issues and etc.).  I'm thinking that the milestones system would
be
an easy way to segregate our emailed tickets automatically.  eg. if we
get a feature request for our calendar that goes to 1 email, and
general
help to a second email address, these simply populate the same ticket
system in trac but with different milestones attached to them (or
components as that would be nice to split things up with as well).  So
my question is has anyone does this before, and do I just need to
modify
the email2trac.py program or do the .c and .h files get modified as
well.
-Garrett McGrath