[Device Discovery] The users misunderstand the field Parent to be the machine/device they are adding an interface to
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Undecided
|
Unassigned |
Bug Description
MAAS Version 2.2.0 (alpha1+bzr5562)
The users misunderstand the field Parent to be the machine/device they are adding an interface to.
The user testing sessions showed the users are not aware they can add container information in MAAS. Thus, they They don’t know that they can specify children for containers. They perceived the field "Parent" as the "parent" device/machine of an interface
* Current result:
Given I am in the device discovery table
When I am adding a device and I see the Parent field
Then I have the impression that the selection of parent is the selection of the device/machine i will add an interface to
And when I change the type of the thing I am adding to Interface I am surprised that the field Parent goes away.
* Expected/ correct result:
Given I am in the device discovery table
When I am adding a device and I see the Parent field
Then it should be clear to me that Parent is the field for selecting the container of a child device
Adding a container seems very different compared
to the other types of devices. I think that we need to surface it as a single option in the initial Type dropdown. This will result in less confusion around the Parent field and also inform the users about the container capabilities in MAAS.
Changed in maas: | |
milestone: | none → next |
status: | New → Triaged |
Changed in maas: | |
status: | Triaged → Confirmed |
Changed in maas: | |
milestone: | next → none |
This bug has not seen any activity in the last 6 months, so it is being automatically closed.
If you are still experiencing this issue, please feel free to re-open.
MAAS Team