Problem:
Currently, a redundant entry can be made as a label and alias. This leads to unwanted redundancy.
If the label in language X is edited to become the same as one alias in language X, the old label is lost. This lead to a loss of data.
Solution:
Any attempt to add a label or alias that duplicates an existing label or alias in the same language should be rejected on the server-side. The user should get an explanation and call to action to solve the problem.
Copy of the error message:
- TODO
BDD:
Reject duplication of labels or aliases in the same language
GIVEN an Item or Property
WHEN trying to add a label or alias that duplicates an existing label or alias in the same language
THEN the edit is rejected
AND the described error message is shown (see copy)
Acceptance criteria:
- Reject duplication of labels or aliases in the same language
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:
BDD (similar to T212869):
Acceptance criteria:
- Given any Item or Property, it's not possible to save a pair label-alias with the same content in the same language via any interface.
Open questions:
- Does it happen that, in order to convert an alias into a label, some software tries to add the label first (first edit) and then delete the alias (second edit)?