Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-17027

Creating ssh key via sourceTree deactivates Save button

    XMLWordPrintable

Details

    Description

      This is a bug report about a minor detail in the account settings dialog of SourceTree, where the save button is deactivated when actually needed.

      Environment:
      Mac OS X 10.13.6
      SourceTree 2.7.6

      What I did:

      1. I create my account details in SourceTree. An old ssh key, [name]-Bitucket.pub, was automatically recognized.
      2. I deleted that automatically recognized ssh key and all bitbucket-related savings in known-hosts, config, etc.
      3. I went back to my account settings in Bitbucket, which now shows a warning triangle, because there is no ssh key found. (I call this, for the sake of reference, "pop-up window 1")
      4. I click on "Create SSH key" (or whatever that button is called): a new window is opened - "pop-up window 2" - and offers to enter a password phrase. I enter the password phrase and click close. The "pop-up window 2" closes.

      What I would expect:

      Being back in pop-up window 1, I now expect to be able to click the save button in order to save my new settings.

      What really happens:

      The "Save" button is disabled, only cancel is possible.

      Remark:

      Since the SSH key was created and saved in the step with "pop-up window 2", and SourceTree recognized a generated SSH key automatically, it might be correct that my expectations of having an active save button available now - after adding an ssh key - are wrong, because everything is indeed saved as a click on "Cancel" and a re-opening of the account settings proves. However, it is misleading, since I just added a new configuration - the ssh key - to my settings...

      Attachments

        Activity

          People

            Unassigned Unassigned
            3e4c6bb9fa55 rowild
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: