Custom Query (332 matches)
Results (91 - 93 of 332)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#111 | fixed | Imported tickets using verbatim format have blank first line in description | bas | planktr@… |
Description |
Imported tickets (when using verbatim format) have blank first line in description, which is removed when editing the ticket with the Trac UI. So Trac is incorrectly reporting a diff on the Description when nothing was really changed other than the blank line that was deleted. Btw, I have applied the mod suggested in ticket:110 to correct issue with attachment imports on Windows. |
|||
#115 | fixed | Imported tickets have resolution set to fixed even though status is new | bas | planktr@… |
Description |
When email is imported, the tickets have resolution set to "fixed" even though status is "new". The resolution remains "fixed" unless the ticket is closed with a different resolution. I have set the following parameter in the email2trac.conf to try to force no value to be used for resolution but it did not work: default_resolution : |
|||
#329 | fixed | initial import of threaded mbox to ticket, and subsequent upgrades | bas | pinto@… |
Description |
Hi there, I'm in the initial stages of educating myself on what can be expected from email2trac. I'd like to do a bulk import of the whole support mailbox, and have the tickets threads recognized and build from the threads in the mailbox, using this syntax: email2trac < ~/mail/support However the whole mailbox is being imported as a single new ticket, including the raw attachments. Subsequently I'd like to run the same above command every couple of minutes (via a crontab), and have the utility update trac only with the new emails or replies. However the whole mailbox is being imported as a single new ticket again. Reflecting back, the suggested installation exercise kept creating a new ticket every time I ran it again, and that was completely unexpected. email2trac < msg.txt Am I expecting too much? Thanks Jaime |