[MGNLDAM-378] Improve handling of multi-language assets during migration Created: 20/Jan/14  Updated: 01/Feb/14  Resolved: 22/Jan/14

Status: Closed
Project: Magnolia DAM Module
Component/s: None
Affects Version/s: 1.2.1
Fix Version/s: 1.2.2

Type: Bug Priority: Critical
Reporter: Magnolia International Assignee: Eric Hechinger
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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
Epic Link: migration_to_5.2.2

 Description   

i18n image links to dms or uploaded ones have to be correctly handled during migration.
For example if two languages are supported (default en, and de)
An image field may be set to support i18n.
If in en, the image refers to a dms image and
the de image is uploaded both images have to be correctly migrated.
Same if both are uploaded or linked to dms.


Generated at Mon Feb 12 04:59:14 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.