[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: |
|
||||||||
| 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)
|
||||||||
| 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:
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 This story thus captures all planned usability changes. I've attached a PDF prototype As a next step after these |
| 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. |