Allow multiple target versions
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.
#5 Updated by Kiall Mac Innes about 9 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!
#6 Updated by Andy Bolstridge about 9 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.
#11 Updated by Eraldo Girardi over 7 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.