Custom Query (332 matches)


Show under each result:

Results (145 - 147 of 332)

Ticket Resolution Summary Owner Reporter
#197 fixed DiscussionPlugin support bas ibarton@…
Hello, email2trac developers.

I'm a developer of DiscussionPlugin for Trac [1] and one of its users
requested an e-mail posting support for it [2]. I see that a good way to
implement this would be to extend your email2trac set of scrips so I'm asking
if would it be acceptable for you to include to mainstream possible patch that
would add DiscussionPlugin support to email2trac or should I fork/reuse
email2trac (or something else) in standalone solution or start to implement
something from scratch?

I haven't studied email2trac code much for now so I don't know how to do it
exactly yet, but in case of possitive answer, I'd digg more into it. Anyway,
any hints or advices would be appreciated.

Thank you for making your stand on this topic.

[1] -
[2] -

With best regards,
#196 fixed The usage of a slash ( / ) in subjects is not permitted when forwarding bas jcuppen@…

The slash is occurring to be an directory slash

  • Tested version is email2trac-1.1.0
#195 fixed Enhancement for ticket prefixes bas Konstantin Ryabitsev <icon@…>

Some of the requests we receive need to be created with a closed status. It's kind of silly, but we need a record of the request for reference, but we don't want the ticket to be open because it's not an actionable item.

This is easy to accomplish using projects and ticket prefixes, but the following patch was necessary to be able to set status and resolution. There's really no reason why resolution should be excluded from the list of fields -- it just limits someone's options. :) Same goes for status.

Note: See TracQuery for help on using queries.