[1.8 UI] Lacking user feedback in action panel

Bug #1454132 reported by Carla Berkers
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Medium
Unassigned

Bug Description

User feedback on the action panel can be improved. Attached design addresses the following issues:

- action title provides summary of what the user is about to do
- deactivated action config when the action is kicked off means user can see in detail which action is being executed
- when there is an error on starting the action, config is reactivated so user can easily amend and retry

Note: stack-able notifications will be implemented as part of this bug: https://bugs.launchpad.net/maas/+bug/1437231

Tags: ui ux
Revision history for this message
Carla Berkers (carlaberkers) wrote :
Changed in maas:
milestone: none → next
Revision history for this message
Blake Rouse (blake-rouse) wrote :

I think the one problem with the design is that the nodes stay selected after the action is completed. That means the user then has to deselect the nodes to perform a different action, this seems weird and more work for the user. Another problem is on the delete action there will be nothing to remain selected, so in that case you have two ways things are done.

1. When an action is finished the nodes remain selected.
2. When a delete action is finished no nodes will be selected.

This give things differently to the user based on the action, which I think will be weird on the user.

Also the larger title for the action I think will look weird when there are no options for that action. Its almost redundant information because you also have the selected action in the call to action button above.

description: updated
Revision history for this message
Andres Rodriguez (andreserl) wrote :

This needs more discussion!

Changed in maas:
importance: Undecided → Low
status: New → Triaged
importance: Low → Medium
summary: - 1.8b4 Lacking user feedback in action panel
+ [1.8 UI] Lacking user feedback in action panel
Revision history for this message
Carla Berkers (carlaberkers) wrote :

hi Blake,

following Marks feedback and our conversation last week, nodes should stay selected.
do you feel comfortable progressing on this bug?

thanks,
Carla

Revision history for this message
Andres Rodriguez (andreserl) wrote :

I believe that this is no longer an issue. I'm going to mark this bug as invalid. If you still believe this issue exists, please re-open the bug report or file a new one.

Changed in maas:
status: Triaged → Invalid
Changed in maas:
milestone: next → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.