Feature #3012
closed
version field request
0%
Description
I am checking up "Redmine" to change issue tracking system from "JIRA" to "Redmine".
But there are some problems for change.
- allow the version field on an issue to assign multiple versions.
- add "affected version" field. (means which versions are affected by the issue)
- add "multiple select" custom field. (Feature #1189)
Our project management system like this.
Core-Module (Package/Framework)
|- Project A (customize for CustomerA)
|- Project B (customize for CustomerB)
|- ...
If I fix core-module, the issue has much effect on some projects. So I want you to support multiple select version field.
We can change to "Redmine" if there features include in version 0.9.
I want you to think about these features.
Updated by takuro monji almost 16 years ago
typo:
I want to append some features as follows.
=> I want you to append some features as follows.
Of course, If you cannot, I'll append these features by myself.
But I want you to support these features as official functions.
Updated by Robert Pollak over 15 years ago
We would also like to have an "affected version" field. But I just found the "custom fields" feature. This might cover our use case.
Updated by Dipan Mehta almost 12 years ago
This functionality is now possible out-of-the-box using custom field of type "version".
This issue should be closed now.
Updated by Toshi MARUYAMA almost 12 years ago
- Due date set to 2013-04-30
- Status changed from New to Needs feedback
Dipan Mehta wrote:
This functionality is now possible out-of-the-box using custom field of type "version".
This issue should be closed now.
I have set due date.
Updated by Dipan Mehta almost 12 years ago
Updated by Daniel Felix over 11 years ago
- Status changed from Needs feedback to Closed
This seems to be resolved. As there is no other feedback, I'm closing this issue.