Feature #5272
closed
Allow multiple target versions
0%
Description
Assume you develop two major branches of a project, e.g. maintaining a 1.x branch while developing a 2.x. branch. When you now have issues that affect both branches (or features that will be implemented for both), there is no way to indicate, that they will be implemented or fixed in/for both. So it would be cool to be able to assign multiple versions as target versions.
Related issues
Updated by Eraldo Girardi about 14 years ago
This would be a useful feature. In my company we have different branches to mantain, and always there are bugs affecting more than a single one.
Updated by Nigel Jones about 14 years ago
I agree this would be a useful feature.
Updated by
Updated by Daniel Miller almost 14 years ago
This feature-request might be a duplicate of feature-request #284.
Updated by Kiall Mac Innes over 13 years ago
+1 There are many other tickets for the same thing, but none have had any activity 9-10 months, and some for years.
This is a really important feature for many developers! We're maintaining 2x versions of the KohanaPHP framework in redmine and struggling to come up with a usable workflow!
Updated by Andy Bolstridge over 13 years ago
A suggestion: it would be useful to be able to automatically create sub-issues (or related issues) for all versions in a project.
eg. you have version 1.0 and version 2.0 to support, when a new bug is found and created, it wil automatically have related/sub issues for all versions, so that they can either be marked 'not a problem for this version' or 'waiting to be fixed in this version'. Then the bug will not be closed until its resolved in all active versions.
It might be better to handle as an option on new issue creation, but it might help a lot of projects that support several versions at once.
Updated by
Updated by Terence Mill almost 13 years ago
Could be resolved by custom field if multiselect support #1189 will be implemented.
Updated by Tharuka Pathirana almost 13 years ago
Updated by Terence Mill almost 13 years ago
In general multiselect switch feature should be possible for all fields, also custom fields of type list or enumeration.
Updated by Eraldo Girardi over 11 years ago
Tried to use a multiselect custom field but it's so different from the default Target version field.
Target version is useful because you can click on it and see what issues are related to that version. This doesn't work with multiselect version custom field.
So I really hope multiple target versions is implemented into Redmine.
Thanks
Updated by Joel SCHAAL over 11 years ago
Can we have some update on what will be decided for this task ?
It has been entered more than 2 years ago and it is still new.
Is this a rejected issue ? Does this issue depend on other work ?
Updated by Anthony BOUQUET about 11 years ago
+1 for this feature, really need this for our project instead of copying/pasting issues to multiple milestones !
Updated by
Updated by Michael Lo about 11 years ago
I am sponsoring a fix for this. Hope to have a test version soon.
Updated by Prof. Dr. YoMan about 11 years ago
I falsely issued a duplicate of this, but from what I see it is a more than once requested feature.
Why isn't it anywhere on the roadmap?
Updated by Toshi MARUYAMA about 11 years ago
- Status changed from New to Closed
- Resolution set to Duplicate
I close as duplicate with #1266.
Updated by Alice Etchegaray almost 10 years ago
+ 1 !!
Michael Lo, have you succeed in developing a fix for that ??
Updated by