Question

When renaming entries in a custom field drop-down list, the cases which had the old entry attached, still have the old value attached.

Reproduce:

1. create a Dropdown custom field with at one value 'something'.
2. create a case with the custom field set to 'something'.
3. in the created Dropdown custom field change the value 'something' into 'something different'.
4. open the case created in step 2

Expected: The custom field should have the value 'something different'.

Observed: The custom field has the value 'something'.

I can see this might not be easy, as it would require Fogbugz to decide whether an entry has been renamed, or just removed and a new entry added. However, it can result in confusion, as renaming an entry will result in 'old' (pre rename) cases not showing in filters using the new value, even if the rename just involved fixing a typo.

Case FC2053681

Answer 1

Renaming custom drop-down values is not something that is currently supported by the Custom Fields plugin.

Currently, the selected drop-down value (e.g., "something") is what is actually stored in the database for a case that uses that drop-down so, as you've suggested, renaming a drop-down value will not go back and update any existing database entries using that value.

We have a case open internally to consider adding this functionality.

Please vote up this question to show your support for this feature request!