Mantis Bug Tracker - Forums

Hello all,

We are using Mantis 1.2.4 here to track issues with our applications and as such have one project per application with versions defined on the project page.
Our current process is the following:

Develop on private version
Release for internal testing by test team
Publish to clients

So, depending on who has discovered the version, they would use a different version to report against.
Right now, using default configuration, a "reporter" or a "updater" only ever sees versions that have the "published" field set, only the "developer" (or above) can see all versions.
The problem we face now is that we would like to keep track of the fact that a version has been internally released and so should be visible to "updater" as well as the other usual profiles.
In the end we would have three date fields:

Created
Internally released
Published

This way we could keep track of which version has reached the clients or not.
I could not find a way to configure this directly in Mantis interface or via the config file. Would there be a plugin for this? Or would I have to modify the sources to achieve this?

Thanks
Olivier

Mantis 1.2.4

Maybe another approach can help.
Configure two versions for this:
During development there is one version which is set to released where you append somethinh like "Beta" or "RC" (Release Candidate) to the version number.
So reporters (maybe beta testers on customer side) and updaters (internal testers) can use this version number for reporting.
The other version which is not set to released during development is used to set the target version and fixed in version.

That's already what is done, but we would like to be able not to show the non released versions to the people who don't need to know about them.
And having the two dates would also help tracking when they were marked as released internally or published

Seems I do not really understand what you want to have.

Can you explain why this is not what you need

Well, I did not notice that global variable when I read the config file, but it does indeed look like it would be useful for us if we assume date of creation of version in Mantis = date of internal release.
That will do it, thanks for pointing out this one