Uploaded image for project: 'Sourcetree For Mac'
  1. Sourcetree For Mac
  2. SRCTREE-1930

Sourcetree bookmarks relocates to current desktop/workspace when clicking on dock icon

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 1.8.1
    • 1.7.3
    • General
    • None
    • Mac running Mavericks
      8GB RAM, tons of disk space

      Since upgrading to Mavericks my "Bookmarks" window seems to be a law unto itself, the only way I can get it under control is to manually move it back to it's correct desktop/workspace by using expose, or quit it and re-launch it.

      Every time I click on the Sourcetree icon in the dock it relocates the bookmarks window to whichever workspace I'm currently in instead of going to the SourceTree desktop/workspace.

      The repo windows seem to stay in the correct desktop, which makes it even more difficult to keep control of everything.

          Form Name

            [SRCTREE-1930] Sourcetree bookmarks relocates to current desktop/workspace when clicking on dock icon

            KieranA added a comment -

            OK, I've tested this one and decided the best behaviour based on requirements of various users is the default. This means that if you hide the bookmarks (which can be done by hitting Cmd+B when it's visible and in focus) then whichever space you're on after the bookmarks has been hidden will the space it's restored to. So if you're on workspace 3 and switch to workspace 1 and hit Cmd+B whilst it's visible (visible can mean even if it's behind windows, by the way) then you'll switch to that desktop. OS X now brings that desktop to the front of the desktop list, too.

            If you close the bookmarks window, however, when you hit Cmd+B again it will show the bookmarks in your current window. This is an OS X feature. We could control this with more effort involved (remembering which desktop it was on, and the position it was in) but going beyond what OS X intends it to do may be overkill.

            This will be in 1.8.1

            Cheers!

            KieranA added a comment - OK, I've tested this one and decided the best behaviour based on requirements of various users is the default. This means that if you hide the bookmarks (which can be done by hitting Cmd+B when it's visible and in focus) then whichever space you're on after the bookmarks has been hidden will the space it's restored to. So if you're on workspace 3 and switch to workspace 1 and hit Cmd+B whilst it's visible (visible can mean even if it's behind windows, by the way) then you'll switch to that desktop. OS X now brings that desktop to the front of the desktop list, too. If you close the bookmarks window, however, when you hit Cmd+B again it will show the bookmarks in your current window. This is an OS X feature. We could control this with more effort involved (remembering which desktop it was on, and the position it was in) but going beyond what OS X intends it to do may be overkill. This will be in 1.8.1 Cheers!

            KieranA added a comment -

            Hi Roger,

            We'd love to be able to respond to every issue, however on jira.atlassian.com when you file a bug/feature request it goes straight to the developers (one of whom is me). We try our hardest to respond to all issues but it's very difficult due to the amount we get in various forms. This issue was read initially as I assigned it to myself and assigned a fix version number which means I manually changed the issue because I thought it deserved to be dealt with. Many issues don't get a fix version number as we don't think they are high priority enough to go into a planned future version.

            I'm sorry that we haven't responded to you, I'll keep my eye on this issue and hopefully get around to fixing it in the near future. I worked on this feature not long ago and the behaviour has changed slightly in Mavericks (it was initially tested on Mountain Lion and prior versions of OS X). We did have another report of the same issue so I'm certain what you're saying is correct.

            Sorry for the delay in responding to you, I'll reserve more time to speaking to users personally in the future.

            Cheers

            KieranA added a comment - Hi Roger, We'd love to be able to respond to every issue, however on jira.atlassian.com when you file a bug/feature request it goes straight to the developers (one of whom is me). We try our hardest to respond to all issues but it's very difficult due to the amount we get in various forms. This issue was read initially as I assigned it to myself and assigned a fix version number which means I manually changed the issue because I thought it deserved to be dealt with. Many issues don't get a fix version number as we don't think they are high priority enough to go into a planned future version. I'm sorry that we haven't responded to you, I'll keep my eye on this issue and hopefully get around to fixing it in the near future. I worked on this feature not long ago and the behaviour has changed slightly in Mavericks (it was initially tested on Mountain Lion and prior versions of OS X). We did have another report of the same issue so I'm certain what you're saying is correct. Sorry for the delay in responding to you, I'll reserve more time to speaking to users personally in the future. Cheers

            Roger Ivy added a comment -

            Unfortunately it looks like this bug is not deserving even of a comment from Atlassian.

            Hello Atlassian .... do you guys even read this stuff?

            Roger Ivy added a comment - Unfortunately it looks like this bug is not deserving even of a comment from Atlassian. Hello Atlassian .... do you guys even read this stuff?

            Roger Ivy added a comment -

            This problem still exists in version 1.8.0.3

            Roger Ivy added a comment - This problem still exists in version 1.8.0.3

            Roger Ivy added a comment -

            This problem still exists in version 1.7.4.1

            Roger Ivy added a comment - This problem still exists in version 1.7.4.1

              Unassigned Unassigned
              a80905b56dd5 Roger Ivy
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: