View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0020512||mantisbt||custom fields||public||2016-01-13 11:10||2019-06-16 13:39|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Summary||0020512: Renaming custom fields breaks column configuration|
Let's assume the user has custom field xyz and they have added it to some column configuration (e.g view issues page) using custom_xyz. If the user later changes the name to xyz2, all the configuration whether they global, project specific, or user specific need to be updated to reflect the new name.
This bug probably applied forever.
internally referring custom fields by name is weak as seen here.
and somewhat related: store enumerated values in a more structured way, instead of pipe-separated strings.
+1 for serializing custom field ids. However, we may want to consider savings ids + names if we want to keep readability within Configuration Report page.
regarding custom fields ids and user preferences:
Then, an approach may be to separate CF "technical name" from "display name".
I think we should only care about "technical name" when defining the custom field, and
The "Display name" part should be handled via localization, as described in http://mantisbt.org/docs/master/en-US/Admin_Guide/html-desktop/#admin.customize.customfields.localize
1, 2, right
The problem with that localization:
a more generic related feature, on this issue: 0020305
+1 for @dregad's rules. I have always been recommending having custom fields follow the rules he specified. However, it wasn't enforced and often people needed them to look different and they didn't care about localization or necessarily new about it. They found a name and typed in what they need in it.
The question remaining is how do we go from current model to the new model:
As for the localization issue, it is a separate topic that we can discuss at 0020305.
I think this would be less impact:
"Display name" as a custom-field property cannot be localized right now (from within the application), but this is consistent with other user defined objects, eg: project names.
|2016-01-13 11:10||vboctor||New Issue|
|2016-01-13 11:10||vboctor||Tag Attached: mantishub|
|2016-01-13 16:31||cproensa||Note Added: 0052306|
|2016-01-15 04:03||vboctor||Note Added: 0052316|
|2016-01-15 05:29||cproensa||Note Added: 0052318|
|2016-01-19 04:10||cproensa||Note Added: 0052330|
|2016-01-19 10:58||dregad||Note Added: 0052331|
|2016-01-19 11:12||cproensa||Note Added: 0052332|
|2016-01-26 00:41||vboctor||Note Added: 0052388|
|2016-01-26 01:36||vboctor||Relationship added||related to 0020305|
|2016-01-26 04:03||cproensa||Note Added: 0052391|
|2016-05-27 09:39||cproensa||Note Added: 0053225|
|2016-05-27 11:40||cproensa||Note Edited: 0053225||View Revisions|
|2019-06-16 13:39||atrol||Tag Attached: schema|