A PractiTest customer was telling me about a problem they have with people not writing down their reasons when rejecting a bug, or writing unclear explanations in the Description or Comments fields.
I know exactly what she meant… I also hate this issue plus the fact that since the data is in Free Text it is very difficult to track the reasons and keep statistics (in case you believe like I do in tracking this behavior as part of an on-going improvement policy).
My solution is simple: I create a customized field called Reject Reason with the acceptable values for rejecting bugs in the project. Usually these values are: Not a Bug, Not Clear, Unable to Reproduce, and Duplicate.
I find that by providing a list instead of asking my users to write down their explanation in free text they are more willing to comply.
Also since I have this as a structured list, PractiTest provides me automatically with statistics to keep track of my rejections and make corrections if needed.
Practitest is an end-to-end test management tool, that gives you control of the entire testing process - from manual testing to automated testing and CI.
Designed for testers by testers, PractiTest can be customized to your team's ever-changing needs.
With fast professional and methodological support, you can make the most of your time and release products quickly and successfully to meet your user’s needs.