Unlikely. We will probably get one from each user for each bug.
I like both options.
The submit to sourceforge is perfect for the general public to send in bugs reports. They don’t really know who it is going to or to where, but they are happy to submit them.
The submit via email option I see useful where you are working closely with a tester trying to sort out a bug. You might be generating svn versions for testing and the same/similiar bug is occuring over and over again. Rather than submitting the logs to sourceforge, your tester can use the email option to send them straight to you.
Yes, I agree that it will lead to duplicates. I’m not sure how bad
that is, though. If it’s an uncaught exception that’s hitting a ton
of people, then it’s something we’d want to fix right away anyhow.
So you want a checkbox and a field for a recipient email address?
It might also be useful (unless you can tell already) to have 3 checkboxes
in the report that helps you zero in how the bug is occurring (for
duplication / testing).
These would be:
Have one of these checkboxes required in the report to help filter types of
problems, as the optional ‘what were you doing’ part is sure to have as many
varied responses for the same bug as there are users reporting them and
modules in which they were happening