Mantis Bug Tracker - Forums

I just installed Mantis and love the interface and functionality. I'm a total rookie when it comes to setting up categories for projects. Could someone help me come up with an ideal case for knowing how to break up projects, builds, categories? I know this is vague so let me try to aska couple specific questions:

- I have a v1.0 product and deveopment and am tracking feature requests, some have already been slated for v1.5, some for v2.0. Should I create three projects (1.0, 1.5, 2.0) in mantis?

- How should I handle feature requests?

- Categories? How should I use these? Since I'm working on a web app should I create categories for each page? by function? What do people recommend?

This would go a long way in helping me get setup. Thanks.

My suggestion would be to set up a project per product. You can then set up releases for 1.0, 1.5, and 2.0. The issues can be assigned to releases using the fixed in version field. (This also allows the Changelog to work properly). I would set up the categories to cover major pieces of the functionality of the product, so that you (or others) can find issues that are related.

There is a severity called "feature" that was intended to be used for feature requests.

Good luck...

I use Categories to divide the Issues into broad areas, e.g. with our application: Installation, Database, Graphics, Other.

This gives the appropriate specialist the chance to spot issues of particular relevance.

Perhaps for your web application the categories might be: Installation, Configuration, Page Format, Database, User Admin, Payment System, Other ... ?