about adding fields:
Yes, it is possible to add fields in Mantis and we've already done that,
but in this case there really is no need. First of all one Unit Test per bug would probably not be sufficient.
It's more likely to use several tests (positive and negative tests, different steps within the code etc.).
If so, then one would need several status fields to see if they are implemented, in progress...
In addition there is no automatic workflow or follow up attached to a status change. This then is equivalent to tagging the bug which can be done by other means.
The solution to this is to use build in features of Mantis.
If we want to track Unit Tests we should
a) create them as a separate bug
b) classify them as feature
c) use the same module and category as the original bug (if it is not over all test procedure)
d) link them to the related bug.
That way we have all the status information we need, can follow it up in the known manner and do not need to maintain
additional fields.
