3 ms·
What's the context? For financial transactions or security concerns? Not so much. For creating work product I can evaluate and decide whether to use? Sure.
by pasbesoin 17y ago
What's the context?
For financial transactions or security concerns? Not so much. For creating work product I can evaluate and decide whether to use? Sure. Can I get my information back out, so that I've not lost all my time putting it into the product?
How easy is bug reporting?
Can I document and submit bugs quickly? I mean, I will put in the effort to be thorough, accurate, and concise in my descriptions. But can I do so without fighting the tracking software interface (and/or its host)? Can I easily and quickly track my issues, with update notifications so I don't have to remember to check status manually?
So, is the risk manageable, the effort streamlined, and the feedback responsive?
And, of course, does the product offer compelling features.
Making bug reporting easy seems under-rated to me. Many times, I've found a bug, to give up on reporting it because the process is too cumbersome. And response to submitted bugs motivates me, as well. I appreciate being able to help a communal effort. I don't expect a lot of time and effort returned unless I've found something significant; a status change in the tracker may be sufficient. But shoving bug reports into a black hole of status quickly becomes demotivating.