Comments on: You’ve Got [Mail|Bugs]? http://www.verilab.com/blog/2007/12/youve-got-mailbugs/ Verilab Fri, 22 Aug 2008 02:11:29 +0000 http://wordpress.org/?v=2.6.1 By: Dusty http://www.verilab.com/blog/2007/12/youve-got-mailbugs/#comment-153 Dusty Sun, 16 Dec 2007 07:26:49 +0000 http://www.verilab.com/blog/2007/12/youve-got-mailbugs/#comment-153 E-mail can be used for to-do's with folders. Your inbox should be just that, an inbox. If it's informative, it can go into another folder. If it requires action, it goes in Todo. If it's fluff, scan it over and throw it in the trash. That's probably why using a to-do list or bug tracker for e-mail correspondence doesn't work as well. There's quite a bit of fluff that you get through e-mail. On the other side of things, tracking bugs through e-mail would limit all kinds of metrics and change tracking that management, bean counters, and excel graph afficiandos everywhere love. This is a big part of some process driven businesses. However, there's nothing to say you can't use a bug tracker centralized database with e-mail. Send your bug report to bugs@myproj and it could be tracked by the daemon reading it while sending an e-mail to the developer to look at it. It's all about how you format the text and if the daemon is smart enough to figure it all out so you aren't wasting more time trying to format your e-mail message. E-mail can be used for to-do’s with folders. Your inbox should be just that, an inbox. If it’s informative, it can go into another folder. If it requires action, it goes in Todo. If it’s fluff, scan it over and throw it in the trash. That’s probably why using a to-do list or bug tracker for e-mail correspondence doesn’t work as well. There’s quite a bit of fluff that you get through e-mail.

On the other side of things, tracking bugs through e-mail would limit all kinds of metrics and change tracking that management, bean counters, and excel graph afficiandos everywhere love. This is a big part of some process driven businesses. However, there’s nothing to say you can’t use a bug tracker centralized database with e-mail. Send your bug report to bugs@myproj and it could be tracked by the daemon reading it while sending an e-mail to the developer to look at it. It’s all about how you format the text and if the daemon is smart enough to figure it all out so you aren’t wasting more time trying to format your e-mail message.

]]>