Details
-
Bug
-
Resolution: Timed out
-
Medium
Description
When we update the label of a SSH Key in our Team Account, the key will be removed and transferred to the Individual Bitbucket Account, but there's no indication that this has happened. Trying to add the key again fails because it already exists in the individual user settings.
Workaround
Remove the SSH Key from the Individual Bitbucket Account and add it back to the Team Account.
Attachments
Issue Links
- is duplicated by
-
BCLOUD-16175 SSH key was deleted without audit log; unable to add ssh key again
- Closed
-
BCLOUD-16368 Saving SSH keys after edit results in deletion
- Closed
-
BCLOUD-16705 Saving SSH keys within Team settings after edit results in moving to user settings
- Closed
- is related to
-
BCLOUD-16943 After closing the edit SSH key or Branch permissions dialog box, the next attempt to edit it will instantly close the box.
- Closed