Looking for Mantis "Best Practices" Guide

[Tinjaw]

I have several people in my group who have never used bug tracking software before and I would like to get them using it properly from day one. I am hoping somebody has written a "Best Practices" guide for using Mantis. I am interested in topics like how to determine what categories to add, how to be handle workflow through Mantis from feature request to it being added to the product and being tested.

My Googleing of "Best Practices" and Mantis only finds articles that state that using Mantis is a best practice, but not how to use Mantis.

thanx

[Nycto]

This doesn't cover all the topics you're asking about, but they are good reads as far as bug reporting goes:

How to Report Bugs Effectively:
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html

Mozilla's Bug writing guidelines:
http://developer.mozilla.org/en/docs/Bu ... guidelines

PHPs Bug writing guidelines:
http://bugs.php.net/how-to-report.php

How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

[Tinjaw]

Thanks Nycto. Those will be very useful for the folks with reporter permissions. And I have already sent those links to those folks.

However, my interest is more for the people who will be processing the bugs. For example, first acknowledge the report, then confirm it can be reproduced, etc., all the while making the proper atomic updates in Mantis.

[Bongalsonado]

tinjaw wrote: However, my interest is more for the people who will be processing the bugs. For example, first acknowledge the report, then confirm it can be reproduced, etc., all the while making the proper atomic updates in Mantis.

Think a good understanding on the defect life cycle in Mantis could help on this. You may visit my blog, join the QAST Practitioner Group, and download the Defect Workflow material in MS Word version at: http://www.daniloalsonado.com/blog/the- ... ing-system

Cheers!