Hello world,
by default, Mantis does not allow bug reporters to specify an affected version that is not yet released (only released versions appear in the list). Is there really no config option to change this?
If not, I'd like to suggest an option that lets reporters also specifiy non-released versions. This is because we often deal with internal testers that should be able to report issues with not-yet-released beta versions.
What do you think?
(Please also reply if the option already exists and I was just too blind to find it, or if you know a workaround.)
Jens
Selecting non-released versions
Moderators: Developer, Contributor
Re: Selecting non-released versions
I believe this issue was raised before. The way I would handle this is as follows:
1. Support for Internal flag.
2. Internal version are only visible for users above a configured threshold (default: DEVELOPER). This applies to drop downs, filters, changelog, roadmap.
3. To take it one step further, apply to view issue (view, print, email, etc), version columns in table views (view issues, csv, etc), issue history, etc.
The simpler solution:
1. User above a configured threshold can choose un-released versions, the rest is as is.
1. Support for Internal flag.
2. Internal version are only visible for users above a configured threshold (default: DEVELOPER). This applies to drop downs, filters, changelog, roadmap.
3. To take it one step further, apply to view issue (view, print, email, etc), version columns in table views (view issues, csv, etc), issue history, etc.
The simpler solution:
1. User above a configured threshold can choose un-released versions, the rest is as is.
Migrate your MantisBT to the MantisHub Cloud
Re: Selecting non-released versions
I would definitely vote for the simpler solution, maybe combined with a new user status "beta tester" above the normal "reporter".
What I dislike about the first solution you suggested is that it would require beta versions to be created as extra versions in Mantis (with the "internal" flag set). I would rather like to consider beta builds and the respective final (release) build to belong to one and the same "version" in Mantis, with the only difference that it is "beta" as long as it is not yet released.
The simpler solution *allows* to do this, but does not *require* it (you can still create betas as separate Mantis "versions" if you like). That's why the simpler solution is not only simpler, but also more flexible.
What I dislike about the first solution you suggested is that it would require beta versions to be created as extra versions in Mantis (with the "internal" flag set). I would rather like to consider beta builds and the respective final (release) build to belong to one and the same "version" in Mantis, with the only difference that it is "beta" as long as it is not yet released.
The simpler solution *allows* to do this, but does not *require* it (you can still create betas as separate Mantis "versions" if you like). That's why the simpler solution is not only simpler, but also more flexible.
-
- Posts: 6
- Joined: 18 Dec 2008, 11:15
Re: Selecting non-released versions
ehm... but the 'solution' is applicable now on mantis or is an 'could be sometime'? 

Re: Selecting non-released versions
I can not use un-released versions even as an administrator in mantis 1.1.6
How do I do that?
How do I do that?
Re: Selecting non-released versions
It could be, patches welcome...MastroWallace wrote:ehm... but the 'solution' is applicable now on mantis or is an 'could be sometime'?