View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004683 | mantisbt | custom fields | public | 2004-10-08 16:41 | 2005-04-18 10:29 |
| Reporter | TomR | Assigned To | vboctor | ||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | fixed | ||
| Product Version | 0.19.0 | ||||
| Fixed in Version | 1.0.0a1 | ||||
| Summary | 0004683: Is there a way to localize enumations of custom fields? | ||||
| Description | To be true multi-language, one should be able to translate also enumaration/selection lists etc. | ||||
| Additional Information | Same applies for Category. | ||||
| Tags | No tags attached. | ||||
|
Currently you can localise custom field names, but not their possible values. This should be possible once 0004451 is implemented. We may also consider having a way to do it without defining a custom function. Please report another issue for customizing categories. |
|
|
This can be achieved using custom functions as described in 0005180. This feature is now in CVS and will be included in 0.19.3. |
|