Three questions : subprojects/categories/fixed in version

mantisNoob · Post by **mantisNoob** » 27 Mar 2006, 02:50

Hi. I've just started using Mantis. It looks good and should suit my needs.
I have a few questions though.

1. Should I create a different project for each release of my software? I've read some other threads regarding this, it looks like maybe creating a main project and then sub projects might be the way to go.
If you do it this way then what should the parent project be? Should the parent project just be a place to hold the other sub projects or should actual issue tracking be going on there?

Here is the related thread I found:
http://forums.mantisbt.org/viewtopic.ph ... b+projects

Also, are there any _live_ installations of Mantis anywhere with public access so I can
see how people are setting up their projects with it? I'd appreciate some links if you have any.

What about reporting bugs in the trunk when there really isn't a release associated with it?

(Sorry for all these sub questions)

2. Is there a convention for creating categories? Is creating a "bugs" category for each project good enough?

3. I've read about the "Fixed In Version" field but I don't see it anywhere in my installation. Is this enabled by default? I'm running version 1.0.1.

Any help is much appreciated.

leblancma · Post by **leblancma** » 28 Mar 2006, 13:56

Hi Noobie,

I'll try to answer your 3rd point

3. I've read about the "Fixed In Version" field but I don't see it anywhere in my installation.

In order for "Fixed in Version" to appear, you must first define versions in the project. Go to Manage » Manage Projects and select the project for which you wish to define versions. You should see a "Versions" box just below "Categories". Type in a version number in the empty field and click on the "Add Version" button.

If you have already defined your versions and "Fixed in Version" does not appear, be sure that you are using the Advanced view. "Fixed in Version" should appear on the same line as "ETA". You can configure the signon defaults to go to the advanced view automatically by doing this

# In file config_inc.php add the following
# --- account pref defaults -------
$g_default_advanced_report = ON;
$g_default_advanced_view = ON;
$g_default_advanced_update = ON;

Regards,

Maurice

mantisNoob · Post by **mantisNoob** » 28 Mar 2006, 16:21

Thanks. I got that working. Should the "fixed in version" field be filled out every time you fix a bug? Or is it just for special uses?

Going back to my question number 1 in my original post; the great thing about using a scrpting language like PHP is that I don't really have to build anything to test it, I just test my working copy any time I want. But now that I'm using bug tracking software, should I create a "tag" in my version control software every time I want to test so that if bugs are found they can be filed under a specific version?

mantisNoob · Post by **mantisNoob** » 28 Mar 2006, 23:47

I've been playing around some more with my installation of Mantis and what I'm thinking of doing to track bugs in the current SVN Head(I'm using Subversion version control) is this:

- Add a "SVN HEAD" version to my "Versions" field

- If the bug is reported AND fixed in between releases I'll set the "fixed in version" field to the next expected release. So for example if the bug is reported and fixed in the current SVN HEAD and the last release was 0.1.1 then I'll set the "fixed in version" to 0.1.2. That way it will show up in the change log for 0.1.2. I've done tried this and it seems to work. The only downside is I have to be sure of the next release version number. I'm not sure if things could get screwed up doing it this way.