We also face this issue in Strapi 5.

Our setup:

• Collection type with localized fields (title, summary)

• Non-localized fields (relations to Cryptocurrencies, Protocols, plus a URL text field, enum sentiment)

Problem:

When we create a new locale for an entry, all relations are dropped and need to be re-assigned. This is very time-consuming and error-prone. We expect non-localized relations to be shared across locales just like enums or simple text fields marked as non-localized.

Feature request:

• Allow relation fields to be marked as non-localized (shared across locales).

•When creating a new locale, preserve all non-localized relations automatically.

•Update the UI so globe icon only shows on localized fields, not on shared ones.

This would make multilingual content management much smoother, especially for projects with many relations (categories, protocols, cryptocurrencies, etc.).

Hello any news about this topic ? It's getting worst since the version 4.15.x I cannot fill anymore from another language if I haven't save before my content. It's starting to be realy hard to contribute in multilang.

Hello, we have a similar issue. Our content is available in 4 different languages: English, Thai, Russian and Chinese.

We are using relations to create content categories and subcategories and we have commissioned the category’s translations to an external translation service.

The problem comes when we create new content and we need to assign a category or subcategory, because nobody is able to read Chinese (for example).

It would be great to keep relations synched in different laguages or at least the “default” language in brackets near the relations.