My users keep forgetting to include an important piece of information in their bug reports. It drives me crazy. I want to require that users fill in two fields before they're able to submit a bug report, but FogBugz doesn't seem to allow me to do this.
|
5
|
|
|
|
|
7
|
It comes down to one thing: friction. Every time you force the user to make a decision, however small, it increases the difficulty of using the software. Telling a user they can't submit a case until they've made a decision about what should be in this required field is, in effect, rejecting them. And we do everything we can to make FogBugz not reject user input. We've helped customers write API scripts that will, on a case being entered, check the field against a set of allowed values, and, if the correct value isn't in there (or if the field is blank) assign the case back to the submitter with a note to put in correct values. These have worked very well. Do we know best? Certainly not. We're not doing this because we're arrogant jerks who know what's best for everyone. It's a business decision, not a religion. But we believe that FogBugz is easy to use because of this design decision. |
|||||
|
|
4
|
To add to what Rich has already answered, you want your system so frictionless that even developers who find bugs as they browse through your code would think to themselves "I'll just put this into our bug tracking software" instead of "I'll just fix this on my way through here". |
|||
|
