[MGNLUI-3910] Usability improvements in the "move" chooser dialog Created: 10/May/16  Updated: 26/Mar/18  Resolved: 06/Jul/17

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: None
Fix Version/s: 5.5

Type: Epic Priority: Neutral
Reporter: Andreas Weder Assignee: Andreas Weder
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: JPEG File IMG_0219.jpg    
Issue Links:
Relates
relation
is related to MGNLUI-3895 Small layouting problem in the "move"... Closed
Template:
Epic Name: AX: "Move" dialog imprv
Acceptance criteria:
Empty
Release notes required:
Yes
Documentation update required:
Yes
Date of First Response:

 Description   

The "move" operation is a continuing source of problems for users. It's a complex topics that requires gradual improvements.

Our move dialog is the only solution for moving items that works consistently across all platforms and input methods. While it does cause a disruption in the user's flow by opening a dialog, it also has advantages, e.g. for the use case of moving items across large distances.

This epic captures a first set of usability improvements we plan to bring to the "move" dialog with Magnolia 5.5:

  1. Adjust column widths to allocate more space to the node column
  2. Reveal root node to make it clear how to move to the top-most folder.
  3. Avoid confusion and having to navigate to the location the move started from by opening the dialog in same location where move started and by revealing the moved item.

Generated at Mon Feb 12 09:11:21 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.