Feature #5272
Allow multiple target versions
| Status: | New | Start date: | 2010-04-08 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | Roadmap | |||
| Target version: | - | |||
| Resolution: |
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.
History
#1 Updated by Eraldo Girardi about 2 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.
#2 Updated by Nigel Jones about 2 years ago
I agree this would be a useful feature.
#3 Updated by Alexander Usikov about 2 years ago
+1
Need for this feature
#4 Updated by Daniel Miller about 2 years ago
This feature-request might be a duplicate of feature-request #284.
#5 Updated by Kiall Mac Innes over 1 year 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 over 1 year 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.
#7 Updated by Pavel Konstantinov 10 months ago
+1
Need for this feature
#8 Updated by Terence Mill 10 months ago
Could be resolved by custom field if multiselect support #1189 will be implemented.
#10 Updated by Terence Mill 10 months ago
In general multiselect switch feature should be possible for all fields, also custom fields of type list or enumeration.