bug ( i think) with select multiple field

hi,
will i have an answer or that's it ?
Thanks
Regards

Hello

i am not sure what you want me to say
i have explained this in my previous answer

Saving field
- changes field configuration,
- it does not tamper with field's saved values (item's field values)

there is no bug , this is the behavior we have ... instead of trying to do guess what is the old value and what is the new

e.g. you change some values and then some labels, and then flip some labels, and then you reorder some rows and then you delete some value row and then you ... save field configuration  ...
and then we do some magic with stored values and we mess things up

this will never be added in any way

---- > If we were to replace a field value this would be done as a new feature via a different interface at item's manager

sorry i did'nt understood your previous response neither this one : i will try to rephrase to be sure we understand each other :
that you tell me is that i was dooing (first time i use this type of field so maybe ..) : change some value or delete one and recreate this one is something in the field that is not possible in the design ? Mean that is something goes wrong, the only way is to delete and recreate the field ? am i right ?

I would add that I am not asking to create a new feature, I just want to understand .. I am not referring to any ongoing controversy .. I am not a developer and what is obvious to you is not necessarily obvious to me ..

Yes because we arnt have enought relation between old and New value
You Can change label but not value
Change value in field doesnt change older selected value in item
Its not a bug it normal

ok thanks now it's clear so if i read between line the only way is to manage the values of these fields is to use relation and relation-reverse fields ?