Forgot your password?

typodupeerror

+ - How to get non-developers to send meaningful bug r 2

Submitted by DemonGenius
DemonGenius writes "I'm in the midst of a major rollout of one of our primary internal applications at work and we have a beta version available for all the staff to use. The problem here is most of the staff don't know how to send reports meaningful enough to get us devs started on solving their problems without constant back and forth correspondence that wastes both developer time and theirs. Some common examples are: screenshots of the YSOD that don't include the page URL, scaled screenshots that are unreadable, the complaint that wants to be a bug report but is still just a complaint, etc. FYI, from the user's perspective they just send an email, but that email registers in our tracking system. Any thoughts on how to get the non-devs sending us descriptive and/or meaningful reports? Does anyone here have an efficient and user-friendly bug tracking system/policy/standard at their workplace and how does it work?"
This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

How to get non-developers to send meaningful bug r

Comments Filter:
  • Give them detailed instructions and examples. Give them categories to choose from. Also, http://www.mantisbt.org/ [mantisbt.org] is one I like.
  • Having worked professionally in QA, I know how to write a good bug report. But it's not obvious to average Joe. You really have to hold their hand and ask them questions-- you know this. The key is to have a template for them to fill out that invites them to answer the most relevant questions up-front. This is never going to happen if they are writing a free-form email. You've got to get them to fill out a form, probably in a web browser. A good example of such a form is here: https://bugs.opera.com/wizardd [opera.com]

Blessed is he who expects nothing, for he shall never be disappointed. -- Alexander Pope

Working...