[2.1, FUJ] New SSH key entry row is not automatically expanded upon import

[Maria Vrachni]

MAAS bzr5400
The interactions when adding adding an SSH key to the table are not right. When the user adds their keys from a source, the table row appears collapsed in the table.

Bug description:

* Current result:

Given I am in the SSH section of the first use journey
When I import SSH keys
Then I can see the imported row of the SSH key table in a collapsed state

* Expected/ correct result:

Given I am in the SSH section of the first use journey
When I import SSH keys
Then I can see the imported row of the SSH key table in an expanded state
And previously expanded rows collapsed

[OS X Sierra]

[Chrome, 53.0.2785.116 (64-bit)]

[Andres Rodriguez (andreserl)]

@ Maria,

What is not "right" about the interactions. The title should say or imply what the interaction is not right instead of saying it is not right.

Instead of: "[2.1, FUJ] SSH table interactions not right"
It should be more like" [2.1, FUJ] SSH table interactions don't do XYZ correctly" or similar.

That said, I think we don't want to show the expanded table. This could be a very very very long key and I dont think we want to show expanded key entries here.

I think we should have the ability to expand tought.

[Blake Rouse (blake-rouse)]

You can expand the keys at any time. It just not expanded by default.

[Maria Vrachni (m-vrachnis)]

@Andres

You are right, there is no right :)

The interaction I am highlighting is a proposal. Would be a nice to have it in order to see the latest key/source import since we don't have another form of feedback.

[Maria Vrachni (m-vrachnis)]

@Blake

Is this bug open and planned to be fixed for a future release?

During the user testing, the users thought that their key was not added and tried all 3 importing methods, still being unsure about having added the key. Some users noticed the new row in the table, but they commented that there is no way to see the key and this is frustrating.

Automatically expanding the new row and showing the key would solve this problem.

[Adam Collard (adam-collard)]

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