Mantis Bug Tracker - Forums

I have worked with a custom in-house bug tracker whose designer expressed that he was heavily influenced by Mantis. However, the company decided to go with an in-house solution because Mantis did not support releases.

For instance, if I am managing several projects that are in different stages such as "Development" and "Testing," I can more effectively manage if I can "release" a project, and have testers all working with one release

Let's say I have a project called "Foo" which may have numerous subprojects. When the Foo developers hit their milestones, I want to release Foo 0.1 and have my testers test all the milestones.

After the testing stage, I want the developers to be working on Foo 0.2, which will be released when the milestones and bugfixes from 0.1 are complete... and the development/testing cycle continues.

Note that the version number is arbitrary and for internal use only-- it does not reflect a "real-world" release version. Mantis doesn't have to guess what my company's internal release versioning system is.

Does any of this make sense? Is there a way I can hack Mantis currently to get the functionality that I want?

I'm looking forward to a template-ized Mantis! Keep up the good work!

I suppose this can be solved using a custom field. However, it would be nice to be able to click "Apply This Custom Field To All Subprojects." I will make a separate post.