Custom Query (332 matches)
Results (238 - 240 of 332)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #116 | fixed | email2trac to also serve blogs | bas | lucas.eisenzimmer@… |
| Description |
Hi Bas, I have been playing around in order to creating/updating blog posts provided by the FullBlogPlugin. See the code attached. What do you think? The distinction between tickets and blog posts is not satisfying at all, and the dependencies are also not processed yet (meaning that it should still work if the FullBlogPlugin is not installed). Cheers, Lucas |
|||
| #286 | fixed | email2trac site and repository unavailable? | bas | thomas.moschny@… |
| Description |
Hi, what happened to the email2trac site? Seems it is currently unavailable. Hopefully the project is still alive? Regards, Thomas |
|||
| #299 | fixed | Email2trac should not set the resolution attribute when creating tickets | bas | ruediger.kupper@… |
| Description |
What happens: When creating tickets, email2trac sets the default values for ticket attributes, including the "resolution" attribute. The default value for the "resolution" attribute is "fixed". This leads to the rather strange effect of a new ticket being displayed as: "Ticket #<num> (new defect: fixed)" What should happen: email2trac does not set the "resulution" attribute when creating new tickets (that's what trac does when using the web interface). After all, the ticket is not resolved yet. The ticket will then be displayed as: "Ticket #<num> (new defect) |
|||
