[MGNLDAM-631] A duplicated asset should be added right after the asset it duplicates Created: 30/Dec/15  Updated: 12/Oct/16  Resolved: 08/Jan/16

Status: Closed
Project: Magnolia DAM Module
Component/s: User Interaction
Affects Version/s: 2.1.2
Fix Version/s: 2.1.3

Type: Bug Priority: Major
Reporter: Ngoc Nguyenthanh Assignee: Ngoc Nguyenthanh
Resolution: Fixed Votes: 0
Labels: is-time-consuming, pain-point, usability, user-feedback, ux, working-with-items
Remaining Estimate: 0.5d
Time Spent: 0.5d
Original Estimate: 1d

Attachments: PNG File good-imho.png     PNG File not-so-good-imho.png    
Issue Links:
Cloners
clones MGNLUI-2927 A duplicated item should be added rig... Closed
relation
is related to MGNLDAM-529 When an asset is duplicated, the file... Closed
supersession
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: UX pain points 2018
Sprint: Saigon 26
Story Points: 2

 Description   

If I duplicate an item, the duplicate should be added right after that item.

We currently add the duplicate at the end of the same-level list, which causes a lot of pain with long lists of items.

Duplicate asset action use the classs: info.magnolia.dam.app.assets.action.CreateAssetVariantAction
Use NodeUtil.orderAfter(duplicateNode, node.getName()) after copying to reorder



 Comments   
Comment by Roman Kovařík [ 30/Dec/15 ]

Doesn't it belong to the dam module?

Comment by Ngoc Nguyenthanh [ 30/Dec/15 ]

Yes, I think. I need to touch classes in dam-app sub-module

Comment by Federico Grilli [ 07/Jan/16 ]

QA: apparently this doesn't work yet. When I duplicate e.g. /travel-demo/social-icons/google-plus.png I get this

whereas I think I should get something like this

Not sure about changing also the node name to something like foo0.png rather than foo.png0 and the asset name likewise, else one cannot distinguish at a first glance what's the copy and what's the original (unless one looks at the node name) but that would probably be the goal of a separate issue.

Comment by Ngoc Nguyenthanh [ 08/Jan/16 ]

fgrilli A bit delay from requesting permission to upgrade DAM version in ce project.
I'm gonna ping you when the request has been approved.
Sorry when I changed wrong status.

Comment by Federico Grilli [ 08/Jan/16 ]

ngoc.nguyenthanh no worries. Can you pls resolve again the ticket and set it as reviewed? Once latest DAM is in, you can set it as integrated. Thanks.

Comment by Mikaël Geljić [ 08/Jan/16 ]

And confirming, integrating to bundle shortly.
fgrilli can you search/file another ticket to tune the path uniqueness? Would be nice indeed

Comment by Federico Grilli [ 08/Jan/16 ]

mgeljic (megusta) also found and linked a ticket for path uniqueness.

Comment by Mikaël Geljić [ 08/Jan/16 ]

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