Feature #21060
Custom field format with possible values stored as records
| Status: | Closed | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Jean-Philippe Lang | % Done: | 0% | |
| Category: | Custom fields | |||
| Target version: | 3.2.0 | |||
| Resolution: | Fixed |
Description
Introduce a new custom field format that stores possible values as records. That will allow future imporvements like nested values, per project values...
Related issues
Associated revisions
Adds Enumeration custom field format (#21060).
Similar to List format but stores possible values as records.
Adds label_field_format_enumeration string to locales (#21060).
Set locale in tests (#21060).
History
#1
Updated by Jean-Philippe Lang almost 7 years ago
- Status changed from New to Closed
- Resolution set to Fixed
#2
Updated by VD DV almost 7 years ago
Is this feature related with #21149 ?
#3
Updated by Toshi MARUYAMA over 6 years ago
- Related to Feature #21149: Linking "Possible values" for List custom fields to another custom fields of same type. added
#4
Updated by VD DV almost 6 years ago
When future improvements stated in this issue (like nested values, per project values...) will be available?
Please cosider it soon. This issue seems to be closed?! Does it mean that these improvements are dropped?
This improvement is necessary for serious multiproject Redmine implementations. Nice future for Redmine is opening with these improvements enabled. I hope for your feedback soon.