No comments on this for 4 months? Is the model so perfect it does not need any improvement? Or is it so wrong so the only reasonable next step is to scrap it and start over?

That looks like a good example of how a company can use the Mantis workflow. it would be useful if you include the editable visio file.

Thanks for your contribution.

Netres,

Could you upload your visio file

THanks
Paul

Netres,

Does your process allow Reporter to "Reopen an issue" for refining?
Manage : Manage Configuration : Workflow Thresholds

It seems like there should be an ackknowledged feedback option when issues are closed as not valid, not in scope or not reproducible. Otherwise, the Reporters who are less skilled in bug reporting lose the motivation to contribute.

I also like to include a step when an Issue is resolved asking whether the fix requires a revision to User or Developer documentation.

Would anyone be interested in a graphviz version of this model? I have been looking for a reason to use it.

slestak: Graphviz version would be cool :) We don't use visio ...

While interesting, the proposed flowchart is still specific to a given workflow, so it is only useful as an example since it won't be applicable in all cases (e.g. most instances do not allow assigning issues to reporters). As such, I don't think it belongs in the Mantis documentation.