You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because machine and cluster names are used as links it's often hard to copy/paste them. This is especially difficult for machines that have UUIDs for the names and clicking on them opens a new page.
Solution
Add a clipboard copy button in common places/lists that machine names are visible. Putting it on the machine page and cluster page would be a great start. Something right next to the name that makes it easy to click without switching pages.
On machine overview page it would be good to have copy buttons next to the machine UUID and on the hostname field because those are used in different contexts (eg omnictl and kubectl)
Alternative Solutions
An alternative would be to make names not links and have a different way for people to click on machines and clusters but I think that would break behavior and not be as intuitive.
Notes
No response
The text was updated successfully, but these errors were encountered:
Problem Description
Because machine and cluster names are used as links it's often hard to copy/paste them. This is especially difficult for machines that have UUIDs for the names and clicking on them opens a new page.
Solution
Add a clipboard copy button in common places/lists that machine names are visible. Putting it on the machine page and cluster page would be a great start. Something right next to the name that makes it easy to click without switching pages.
On machine overview page it would be good to have copy buttons next to the machine UUID and on the hostname field because those are used in different contexts (eg
omnictl
andkubectl
)Alternative Solutions
An alternative would be to make names not links and have a different way for people to click on machines and clusters but I think that would break behavior and not be as intuitive.
Notes
No response
The text was updated successfully, but these errors were encountered: