[MGNLUI-3761] Fix usability issues of the move method using a dialog Created: 29/Jan/16  Updated: 31/May/16  Resolved: 31/May/16

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

Type: Story Priority: Major
Reporter: Andreas Weder Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: pain-point, team-priority, usability, usability-of-move, ux, working-with-items
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File Move using dialog v3.pdf    
Issue Links:
relation
is related to MGNLUI-3763 Add additional value to the move dialog Closed
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)
Epic Link: UX pain points 2018

 Description   

The 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.

However, our current implementation has a couple of problems, which negate such advantages.

Move using a dialog has usability problems:

  • it opens at the root folder instead of the exact same place you're calling the move from. This disorients the user and requires to first grasp what exactly you're looking at. It also requires to find again the location of the item you move in some cases.
  • there's three "move" buttons to choose from (move inside, above or below the currently selected item), which adds up to four buttons if you also count "cancel". We should offer all options, but not show them at the same time.

We also want to invest into a set of improvements in order to provide significant more value for the user using a dialog to move items. These improvements are described in more detail in MGNLUI-3763.

This story thus captures all planned usability changes. I've attached a PDF prototype visualizing all changes in one go (change your PDF viewer to show a single page only, then click on the link areas marked in red). Note that the PDF prototype also shows a couple of the planned improvements.

As a next step after these fixes and improvements, we'll add quicker, richer ways to alternately move items, but these will depend on the input method and device. The move dialog will (and will have to) remain available and attractive.



 Comments   
Comment by Andreas Weder [ 29/Jan/16 ]

Added this story to the AX epic for now. We will have to create actual issues for all mentioned items and properly priorize these.

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