[MGNLDAM-1115] Uploading content through damLinkField ignores rootPath Created: 17/Feb/23  Updated: 28/Jun/23  Resolved: 26/Jun/23

Status: Closed
Project: Magnolia DAM Module
Component/s: None
Affects Version/s: 3.0.24
Fix Version/s: 3.1.0, 3.0.25

Type: Bug Priority: Neutral
Reporter: Roberto Gaona Assignee: Adam Siska
Resolution: Fixed Votes: 0
Labels: Nucleus_AuthX_Support
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: 0.5d Time Spent: 0.5d
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
causality
caused by MGNLDAM-922 damLinkField: rootPath property not s... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLDAM-1201 Implementation Sub-task Completed Adam Siska  
MGNLDAM-1202 Code review Sub-task Completed Quach Hao Thien  
MGNLDAM-1203 Preint QA Sub-task Completed Quach Hao Thien  
MGNLDAM-1204 QA Sub-task Closed Antonín Juran  
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Release notes required:
Yes
Date of First Response:
Epic Link: AuthorX Support
Sprint: Nucleus 39
Story Points: 2
Team: AuthorX
Work Started:
Approved:
Yes

 Description   

Steps to reproduce

Add the following property to any dialog:

damLinkTest:
  label: Test label
  $type: damLinkField
  required: true
  datasource:
    $type: assetDatasource
    rootPath: "/travel-demo"
    workspace: dam 

Then access it, and upload an asset without selecting any folder at all (use direct upload with bottom-left actions, both upload and upload&edit suffers from this issue). This asset should be stored on "/travel-demo". However, it'll be stored on the root of the dam workspace instead of taking into account the specified rootPath property.


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