|
Hi, Many of the connections you use on a regular basis share a lot of settings (same username, same SSH key, maybe same jump host). Based on that, being able to clone an existing connection to only make the required changes would make the user's life easier. Here is how I see the user experience: There will probably be a need to check the connection name length before adding the extra text in order to avoid going over the limit. If that would be the case, one solution could simply be to not add the extra text. |
Replies: 1 comment 1 reply
|
Proposed in PR #151. Each saved connection now has a localized Duplicate action. It opens the normal editor as a new draft (no source profile ID), pre-populates all editable connection, key, jump-host, group, and post-connect fields, and appends a localized copy suffix while truncating the original name as needed to stay within the 128-character limit. Saving creates a separate profile and cannot overwrite the source. |
Proposed in PR #151. Each saved connection now has a localized Duplicate action. It opens the normal editor as a new draft (no source profile ID), pre-populates all editable connection, key, jump-host, group, and post-connect fields, and appends a localized copy suffix while truncating the original name as needed to stay within the 128-character limit. Saving creates a separate profile and cannot overwrite the source.