[MGNLUI-4951] Improve drop targets for assets Created: 15/Jan/19 Updated: 03/Nov/22 Resolved: 16/Mar/21 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Epic | Priority: | Neutral |
| Reporter: | Anja von Gunten | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | ux-pain-points | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Epic Name: | drop targets improvements |
| Acceptance criteria: |
Empty
|
| Date of First Response: |
| Description |
|
Problem Currently the upload field is the only drop target to drag&drop assets. That target can manage just one file at a time. Batch upload is only possible via zip file or else not possible at all. This means the editor has to upload every file one by one which is a pain. The Magnolia UX needs to catch up on basic ui drop target functionalities. Business value
|
| Comments |
| Comment by Šimon Demočko [ 22/Feb/21 ] |
|
Hi czimmermann, we cannot properly estimate this cause it's lacking acceptance criteria. Are those essentially all issues under the epic, or is there more to it? Also, our biggest concern is if editing assets in Magnolia is something we want to maintain and continually evolve in functionality when the general intention is to have assets in 3rd parties instead. |
| Comment by Anja von Gunten [ 16/Mar/21 ] |
|
Has not been prioritized |