[MGNLUI-2927] A duplicated item should be added right after the item it duplicates Created: 20/May/14 Updated: 15/Apr/16 Resolved: 23/Dec/15 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | user interaction |
| Affects Version/s: | 5.2.5, 5.3 |
| Fix Version/s: | 5.3.13, 5.4.4 |
| Type: | Bug | Priority: | Major |
| Reporter: | Andreas Weder | Assignee: | Ngoc Nguyenthanh |
| Resolution: | Fixed | Votes: | 2 |
| Labels: | is-time-consuming, pain-point, usability, user-feedback, ux, working-with-items | ||
| Remaining Estimate: | 1d 7h 25m | ||
| Time Spent: | 1d 35m | ||
| Original Estimate: | 3d | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||
| 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 25 | ||||||||||||||||||||||||||||||||
| Story Points: | 5 | ||||||||||||||||||||||||||||||||
| 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. |
| Comments |
| Comment by Ngoc Nguyenthanh [ 23/Dec/15 ] |
|
Assumptions: Almost duplicate actions use the class info.magnolia.ui.framework.action.DuplicateNodeAction. But I do a quick search to figure out the similar issues. We need to create tickets to fix if needed.
Solution:
|