Hi shawn, Shawn Hill" escreveu: > 3. Documentation - workflow > Does anyone use mantis to track bugs in documentation. In the example above > if we have a new feature, there should be documentation to support it. I > would like to work off mantis for the documentation, but I am not sure just > yet, as to how to smoothly insert the documentation into the workflow. > Could this be a status between resolved and closed? e.g. > New Bug Feature->Acknowledged->Assigned->Coded->Resolved->Documented->Closed
I think so. I'm now in a similar situation. In the company workflow at this moment after a developer has finished his job the issue's status is changed to Resolved. All issues in the Resolved status are submitted to the approval of the test team. If the test team find some problem the status is changed to Feedback, if they don't find any problem the issue is closed. After it has been closed it is ready to be included in the release version. This workflow has some probems, because we can't know which issues: - were tested; - were documented; - were indeed included in the release version; I'm planning to create three new status, so the workflow would be: New (Bug/Feature)->Confirmed/Acknowledged->Assigned->Resolved->Tested->Documented->Released->Closed Well, this enlargement of the workflow is worrying me. :) But we really need to have a better view over the process. Any comments are welcome. Regards, Jeferson Oliveira Brazil ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ mantisbt-help mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mantisbt-help
