Should we use a bug tracking system to track changing requirements?

Question

I am currently using Mantis to track bugs in my projects, and I like it. Using special categories, etc., I also use Mantis to track new project requirements. I don’t feel comfortable with this workaround, because when I add a new report, many of the text fields that I will be prompted to fill out are associated with an error.

My other alternative to Bugzilla , but it sounds much more bug related.

I need to use only one tracker to configure SVN, etc.

Edit:

What should be the right direction for one developer / several projects ?, or is it normal to save the mantis?

Answer 1

Have you viewed Redmine ? My team used Redmine for almost a year, and it was a dream.

Redmine is flexible in design, allowing you to specify different fields and workflows for each tracker. For example, you can configure various trackers for Errors and Functions, and then allow end users to create new errors, but prevent them from directly adding feature requests. Errors may have a Severity drop-down list, but there will be no problems with Tracker Features.

This is similar to what you are looking for.

Answer 2

Trac " /. Subversion ."