View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0006258||mantisbt||documentation||public||2005-09-15 22:49||2014-11-25 12:48|
|Summary||0006258: Add examples of different workflows|
By far the toughest part of getting Mantis up and running was deciding how to use it, specifying the different bug status values, what they meant and how they could change. It would have been incredibly useful to see some examples of simple/average/complex workflows, with some justification for why each worked and what sort of project/team would use it.
|Tags||No tags attached.|
Is such documentation helpfulness?
[Whoa: blast from the past.]
Mantis is flexible so that you can set it up with a number of different life cycle models. I'm guessing, for example, that most small development teams don't need as many states as that document lists (our certainly didn't). However, each team has to agree on how to handle its Mantis installation's life cycle states, and it isn't trivial to figure this out when you're new to Mantis.
Here's what I wrote up for my team when I originally started using Mantis:
The "Issue life cycle" section is what I was referring to here. There are lots of ways to use issue trackers, and you can't really expect a new user to come up with a plan all on their own. Plus, the needs of the specific group guide the life cycle choice in complex ways. Ideally, you'd have three different examples of life cycles, with some details on how someone would set up Mantis appropriately:
For each scenario, give why it would work for a specific group and why it might not. You might also add some notes on variations:
In summary, Mantis is no good unless the local users agree on how to use it. Anything you can do to help the local promoter clearly document how it will be used will help get Mantis installed more often.
|2005-09-15 22:49||dtgriscom||New Issue|
|2014-10-07 19:08||grangeway||Severity||major => minor|
|2014-11-25 12:27||vboctor||Assigned To||=> vboctor|
|2014-11-25 12:27||vboctor||Status||new => assigned|
|2014-11-25 12:27||vboctor||Note Added: 0041914|
|2014-11-25 12:48||dtgriscom||Note Added: 0041915|