Custom Query (332 matches)
Results (148 - 150 of 332)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#196 | fixed | The usage of a slash ( / ) in subjects is not permitted when forwarding | bas | jcuppen@… |
Description |
The slash is occurring to be an directory slash
|
|||
#197 | fixed | DiscussionPlugin support | bas | ibarton@… |
Description |
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] - https://trac-hacks.org/wiki/DiscussionPlugin [2] - https://trac-hacks.org/ticket/6883 With best regards, |
|||
#198 | fixed | Accept workflow transitions | bas | thomas.moschny@… |
Description |
The ability to specify ticket properties in message body (what was #171) is really helpful. It would be cool to make status changes via specifying TracWorkflow transitions. Instead of @status:closed @resolution:fixed that would read @->resolve(fixed) The difference is be that the transition would only be made if allowed. Not sure this is worth the effort though. |
Note: See TracQuery
for help on using queries.