Mantis Best Practices for Software Develpment

[luizgmk]

Dear All,

I would like to use Mantis to keep track of all software development efforts on many different projects. Basically, just as in Mantis Development itself, I want to keep track of new feature requests, bug issues and so on. I have been looking for examples of how people use Mantis trying to find what are the best practices but all I found were a few comments on the issue tracking flow, the use of versions, the use of auto-assignments based on categories etc, but nothing as substantial as I would like.

The first doubt I have is what would be the best way to associate bugs or features to a software component. We are used to track issues by "Use Case". I am not feeling too conformable about using categories for this purpose. I'm using categories to classify the issue as a bug, feature, enhancement opportunity or process non-conformity.

I also would like to be able to assign issues to subcomponents of the software. I didn't find a way to do this without writing code. Components need to be different from project to project (different software’s) and subcomponents should change according to component selected.

I can't believe no one already does something similar. I would be glad to know how you do it yourself at your company.

Thanks!

[atrol]

I'm using categories to classify the issue as a bug, feature, enhancement opportunity or process non-conformity.
I also would like to be able to assign issues to subcomponents of the software.

You could use "Severity" for classification and use "Category" for your subcomponents

[luizgmk]

Severity has its own importance in issue classification. I want to know whether a non-conformity is of high or low severity. So, I would like that the severity field stay there for its original purpose.

[atrol]

Maybe a plugin which is interesting for you
http://git.mantisforge.org/w/product-matrix.git

[luizgmk]

Maybe a plugin which is interesting for you
http://git.mantisforge.org/w/product-matrix.git

Very interesting plugin! But maybe too complex to what I really need. Anyway I will be testing it and posting comments later.

What I want it today is not to track issues against multiply software versions, variants and etc, but to track them against software use cases. If we were to implement it to Mantis own bugtracker, I would be associating an issue to functionalities such as "Report Issue" ,"View Issue", "Road map", "My View" etc.

I would like to hear from people about how they do it themselves today.. just don't?

[atrol]

If we were to implement it to Mantis own bugtracker, I would be associating an issue to functionalities such as "Report Issue" ,"View Issue", "Road map", "My View" etc.

This is nearly what is configured for MantisBT's own tracker http://www.mantisbt.org/bugs , but we are using the category for it.

Are you aware of the project / subproject feature of MantisBT?
use subproject for your component and create custom field of type enumeration for your subcomponents