Like many software houses, our product is in a constant development/test/review cycle. When we find bugs that only exist in the development version of our product, we'd like to file a bug report against that version. Unfortunately, mantis only lists product versions marked as 'released' in the appropriate drop-down.
This leaves us with two options. We either mark all our version as released, even if they aren't yet released, or we revert to using scrappy bits of paper to record bugs in the development version. Neither of these options is really satisfactory.
What is the rationale behind Mantis' stance on bugs only being able to be files against released product versions? Sure, I could edit the code myself to allow me to file bugs against development versions, but that would make upgrading Mantis much more tricky than I would like it to be.
Reporting bugs against unreleased product versions
Moderators: Developer, Contributor
I think reporting issues against only released issues make sense. However, this is only as far as external customers are concerned. But for internal staff, they should be able to report issues again unreleased versions as well.
Hence, I think there should be a new config option that allows setting an access level threshold above which the user should be able to report issues against unreleased versions.
$g_report_issues_for_unreleased_versions_threshold = DEVELOPER;
Does this fully solve your issue? If so, please put in a feature request in the bugtracker, and feel free to submit a patch if you have the time.
Regards,
Victor.
Hence, I think there should be a new config option that allows setting an access level threshold above which the user should be able to report issues against unreleased versions.
$g_report_issues_for_unreleased_versions_threshold = DEVELOPER;
Does this fully solve your issue? If so, please put in a feature request in the bugtracker, and feel free to submit a patch if you have the time.
Regards,
Victor.
-
- Posts: 1
- Joined: 10 Aug 2005, 14:29