Disadvantages of working in a multilingual version

When working with content with descriptions and names in two languages, there is an inconvenience, for example, they created the name and description of the RU - After that, you need to go into multilingualism, switch the language to the example for SA - the description and name fields will be empty and you need to re-register the fields, and if the task is to make them similar or when using machine translation - this is generally a quest. I tried to create a bridge through an additional field, but importing from an additional field in the UA version is only possible with the UA Version, which can lead to erroneous uploading of content to the wrong language version. A request to the developers to consider such a solution to this issue - so that in one window there are fields from both versions - which would greatly simplify the work of the content manager and he could make descriptions and names for all versions of the site without switching versions https://prnt.sc/ wnipqd