home/about - roadmap - docs - mailing list - downloads/cvs - sourceforge project page - links
In my opinion, the e-mail interface is the holy grail of issue trackers. There is no program that I have open as much or as consistently as my e-mail client. Additionally, I have access to an e-mail client where ever I go. Therefore the ability to do basic chores such as creating new bugs, attaching files or adding comments to bugs through e-mail is a true benefit.
There are many bug trackers out there that have e-mail interfaces, but generally speaking, they ALL suffer the same two problems... Amazingly difficult to satisfy perl module dependencies, and the necessity to hook into the smtp server so that a program can run when ever a new message is sent to the software.
In order to solve those problems and make bug tracking with e-mail easier, my solution requires only that PHP be compiled with IMAP support (actually, a work around exists if you don't have IMAP support, cf. squirrelmail), a way to run a php program at periodic intervals, and a POP3 mail box to send e-mails to.
With those simple requirements, it's a piece of cake to create a PHP command line program that checks a POP3 mailbox at regular intervals, download messages, and process them. A subject line that contains a bug id will be an "edit" request, a subject line without a bug id will be a "new bug" request. The e-mail headers will contain the basic information needed to create a new user in the system (namely, the e-mail address) if the user doesn't already exist.
As a precautionary measure, it's possible to design the e-mail UI script so that it leaves messages in the pop3 mailbox until the bug is verified or assigned. Once the status of the bug has changed, the message can be deleted.