**Problem:**
Instead of adding identical values for many languages, editors will soon be able to add a `mul` Label and Alias in the termbox. It is however not immediately obvious, that the `mul` entries will work as fallbacks. Editors will only see "No label defined" which might convince some editors to add the redundant Labels again. We need to make this more intuitive.
**Notes:**
* The reason is that we only allow the language code `mul` for Labels and Aliases and not for descriptions (T313027).
* We only consider `mul` values as intentional fallbacks. So we only use `mul` values as placeholders and not `en` values.
**Solution:**
If a `mul` label is available, use it as a placeholder for all other existing languages with an empty value.
**Mockups:**
**BDD:**
The `mul` Label/Alias is used as a placeholder for all empty Labels/Aliases when the Item is opened for viewing or editing on both desktop and mobile.
GIVEN an Item with a `mul` Label/Alias specified
WHEN the Item is opened for viewing or editing on desktop or mobile
THEN all empty Labels/Aliases are shown with the `mul` Label/Alias as a placeholder (in gray, see mockups)
When an empty Label/Alias is edited the placeholder value disappears on both desktop and mobile.
GIVEN an Item with a `mul` Label/Alias as placeholders
WHEN an empty Label/Alias is edited on desktop or mobile
THEN the placeholder value disappears
**Acceptance criteria:**
[] The `mul` Label/Alias is used as a placeholder for all empty Labels/Aliases when the Item is opened for viewing or editing (see mockups and BDD).
[] on desktop
[] on mobile
[] When an empty Label/Alias is edited the placeholder value disappears (see mockups and BDD).
[] on desktop
[] on mobile
**Open questions:**
* Is there a need to add "(fallback)" to placeholders? If not then let's avoid this as this would lead to a lot of redundancy (to consider: mobile is red text).
* Do we need this immediately: The moment a user defines (or modifies) a `mul` label and saves, then all other language’s label placeholders become populated with the `mul` label (placeholder style should be maintained).
**Community communication:**
Who we needs to keep in the loop and in what way:
Who this could be interesting for and in what way:
**Original:**