Duplicate location creates new location with old location name

Users duplication tested, also works fine.

> If the name of the new location is changed and saved, the field name in table stock_location keeps the original name and
> saves the new name in ir_translation.
>
Assuming you use a local other than en_US, it's the normal behavior
isn't it?
Lionel Sausin.

Lionel,

That's correct, i'm using es_VE locale, but, why other objects dont have this behaviour (products, users)?
And what about this, if we are using es_VE, then we duplicate a location with name 'Plastic bottles' and
change its name to 'Plastic cups'. The new location still have 'Plastic Bottles' in stock_location table, but then
another user using a different locale (in example, es_PE), edits 'Plastic Cups' because the name was wrong and
change the name to 'Policarbonate bottles'. As the changes are saved in ir_translation, es_VE's users will never
know about this change because they are going to see 'Plastic Cups'.

I dont see why it should be stored as a translation.

I forgot, i have tested using en_US, only in this case the duplicated location saves its new name in stock_location.name

This behavior is "by design", so please let me turn this bug into a question.
Lionel.