[FUJ] It is not clear for users that they need to click on 'Save Selection' to start importing new images

Bug #1650587 reported by Maria Vrachni
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Low
Unassigned

Bug Description

MAAS 2.1, It is not clear for users that they need to click on 'Save Selection' to start importing new images

During the user testing 3/5 users proceeded to the SSH section without importing images because they either missed the "Save selection" button, or they didn't know what it was intended for.

* Current result:

Given I am a first time user in the Images section of the first use journey
When there are already queued images in the list
Then I might miss seeing them and not commit the selection

* Expected/ correct result:

Given I am a first time user in the Images section of the first use journey
When there are already queued images in the list
Then I want to see some visual queue that helps me identify the unsaved changes
And the UI component that allows me to commit my changes should be labeled in a descriptive way

The users didn't expect having to commit changes for selected images. Also, the label is not descriptive of the action and in the user testing there were images queued for download and the users didn't notice it.

[Needs design]

Changed in maas:
status: New → Incomplete
summary: - [FUJ] The save selection button in the Images section causes problems
+ [FUJ] It is not clear for users that they need to click on 'Save
+ Selections' to start importing new images
description: updated
summary: [FUJ] It is not clear for users that they need to click on 'Save
- Selections' to start importing new images
+ Selection' to start importing new images
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for MAAS because there has been no activity for 60 days.]

Changed in maas:
status: Incomplete → Expired
Changed in maas:
status: Expired → New
Changed in maas:
importance: Undecided → Low
status: New → Triaged
milestone: none → next
Revision history for this message
Andres Rodriguez (andreserl) wrote :

** This is an automated message **

We believe this is no longer an issue on the latest MAAS releases. As such, we are marking this bug report as invalid. If you believe this is still an issue, please re-open the bug report and provide any relevant information.

Thanks.

Changed in maas:
milestone: next → none
status: Triaged → Invalid
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.