[MGNLDAM-312] Clarify if we want to be able to add sub assets to an asset Created: 03/Oct/13  Updated: 05/Aug/15  Resolved: 05/Aug/15

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

Type: Task Priority: Critical
Reporter: Andreas Weder Assignee: Mikaël Geljić
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

5.1 RC2 CE


Attachments: PNG File Bildschirmfoto 2013-10-03 um 11.58.23.png    
Issue Links:
Relates
relates to MGNLDAM-476 Allow asset upload when an asset or f... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

I uploaded a new asset in the chooser UI of the Assets app and had a previously added asset selected. As a result, a new asset was created and added as a sub asset to my selected asset (see screen shot).

Is this actually something we want? Should that be possible? If not, I recommend we fix this rather sooner than later (thus the high priority of this issue).



 Comments   
Comment by Mikaël Geljić [ 05/Aug/15 ]

Right now, I can't think of any reason to do this. Besides, this is no longer possible by accident: we've adjusted availability all around (e.g. browser, move actions, direct upload) to prevent that. Therefore if you don't mind I'll close that one with appropriate resolution (may still be reopened if need ever arises).

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