[MGNLDAM-883] JCR Asset content node has incorrect primary type Created: 14/Sep/20  Updated: 18/Feb/21  Resolved: 18/Feb/21

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

Type: Bug Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
duplicate
is duplicated by MGNLDAM-939 JCR DAM has fixed nodetypes for node ... Closed
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
Date of First Response:
Epic Link: Migrate Assets

 Description   

As of MGNLUI-5656 fix the node type of the Asset's jcr:content sub-node is not specified, while it used to be mgnl:resource.

Acceptance criteria:

  • correct node type is used for the new assets
  • affected existing content is migrated


 Comments   
Comment by Simon Lutz [ 18/Feb/21 ]

Please follow MGNLDAM-939 for further updates.

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