[MGNLCT-134] Submodel gets a wrong i18n key Created: 02/Sep/19  Updated: 30/Aug/21  Resolved: 30/Aug/21

Status: Closed
Project: Content Types
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Martin DrĂ¡pela Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File content-type-examples-v60mgnl.tar.gz     File content-type-examples_v612mgnl.tar.gz     PNG File faulty_i18nkey_4_submodel.png    
Issue Links:
Problem/Incident
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

Submodel gets a wrong i18n key, which makes it impossible to i18n the field using a message bundle. See below at the bottom the correct key in mgnl 6.0 (left shot) vs the wrong one in 6.1.2 (right shot, also seen in 6.1):

The following i18n labels were thus displayed only in mgnl 6.0:

tourOffices-app.default.allVehicles.vehicleGroup.vehicle.label = Vehicle tourOffices-app.default.allVehicles.vehicleGroup.amount.label = Amount

Generated at Mon Feb 12 00:37:29 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.