0

We mainly use FB mailboxes internally as a mechanism for linking email and FogBugz; eg send an email explaining a problem or fix and cc FB to add this to the case history.

One of the consequences of this approach is that typos in the email subject, or simply forgetting to add (or correctly format) the "(Case xxxx)" reference, leads to creation of spurious new bugs which then get resolved as dups but we lose some of the context along the way.

It would be nice to be able to designate certain mailboxes as unable to create cases - if you send an email to this address which would create a new bug then you get a templated error response back instead of a new bug being created.

flag

1 Answer

1

Not that this directly solves your problem, but why not send these emails from within FogBugz? Then all the bookkeeping is handled for you automatically.

link|flag
Via the Notify plug-in for instance. – Rich Armstrong♦ Feb 1 2011 at 22:21
I guess in some cases that is the solution, but often it's a case of following-up an existing email discussion thread and 'linking' it to the relevant bug. Also a 'real' mail client provides a nicer environment for composing and sending mail, and is particularly applicable for users who are only occasionally logged in to FB itself. Not to mention users who have remote access to email but not to our intranet - eg via Blackberries etc. – Matt Feb 2 2011 at 9:52
I'm not trying to disagree with you, but I just wanted to let you know that FogBugz 8.3 now has the ability to compose rich text/html emails from directly within FogBugz. There's also a built-in mobile version of FogBugz included as part of 8.3 as well. – db♦ Feb 2 2011 at 14:55

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.