I understand that versions can be either "released" or not,
and that only defects with non-released target versions show up in the roadmap.
One limitation with this though is that we frequently have products which are "internally" released to a small set of users,
and until they are offically released, we still want them to be listed under the roadmap.
The problem is that if bugs are found in this internal release, they can not be logged, as the version number is not available in the version dropdown.
It seems like we need a 2 checkboxes...
"public/private" flag --> determines if the version shows up in the dropdown lists
"released"flag --> determies whether a version shows up in the roadmap.
the other thing this would help with is if versions are no longer usable and you want them to no longer be shown in the drop down lists (if they are no longer supported for example) the version could become "private". If you just changed it to unreleased, it might show up in the roadmap again which is obviously not what was intended.
Thoughts?
internally released versions
Moderators: Developer, Contributor
-
- Posts: 100
- Joined: 14 Aug 2005, 22:47
- Location: new zealand
- Contact:
Re: internally released versions
I think we need three flags:
1. Released
2. Internal (aka private)
3. Archive (old releases that are no longer supported, e.g. remove from drop down lists, change logs, etc)
The question is who should see "internal" releases? My feel is that it should be controlled by an access level with DEVELOPER as the default value.
1. Released
2. Internal (aka private)
3. Archive (old releases that are no longer supported, e.g. remove from drop down lists, change logs, etc)
The question is who should see "internal" releases? My feel is that it should be controlled by an access level with DEVELOPER as the default value.
Migrate your MantisBT to the MantisHub Cloud
-
- Posts: 100
- Joined: 14 Aug 2005, 22:47
- Location: new zealand
- Contact:
Re: internally released versions
I agree 100%