View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0010840||mantisbt||administration||public||2009-08-17 10:01||2010-03-14 07:52|
|Summary||0010840: You can set a 'released version' as the target version|
It is possible to use a version that is marked as released as the target version for a fix. How can something that is released be the target for a fix?
We would like it so this doesn't happen as we are getting users who are confused and simple and keep setting target versions as things that have already gone out the door. This causes issues to not get 'caught' we the manager does a search for all things expected to be in a release.
Is this a bug or a feature?
|Tags||No tags attached.|
This is by design afaik. If you have a bug report where someone forgot to set the target version, but the target version you want to set it to has already been released, you'd still want to be able to select the released version.
It's possible that this could be turned into an option.
Perhaps the released state could be indicated in the list of versions. eg:
version 14 (released)
We already do this manually, by renaming the versions as they are released. But it's a pain to maintain, and it breaks any saved filters using these versions. Having an option to append the state to displayed versions would be good, and still allow users to fix-up "forgotten" issues.
How about having a configuration variable like $g_report_issues_for_unreleased_versions_threshold, but for the "Target Version" field showing released versions? This would also be useful for the "Fixed in Version" field.
At the moment, I've had to go through all the possible pages and change where it shows all versions to only show future versions (replace VERSION_ALL with VERSION_FUTURE).
A threshold value for these would mean that, for instance, a manager could change the value to any version, but a developer would only be able to choose unreleased versions.
Where we are using Mantis, this is also a problem. It would be useful to have an option so that it is possible to make the "target version" show only un-released versions.
I'm from In-Portal CMS community and we are also having same problem, that users are setting target versions to released onces so tasks won't show up in proper places.
Since this issue was unattended for several months, then the best solution is to as suggested in 0010840:0023043.
Also we could also add (during issue editing) currently selected version (product/target/fixed) to be always present no matter is it released or not, so simple even released task editing won't cause version to be lost.