• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 3.0.3
    • 1.9.5.0
    • Git
    • None
    • OS Windows 10

      Bitbucket.org

    • Severity 1 - Critical

      I can no longer select the files I want to commit using checkboxes. The checkboxes are missing! Why?

            [SRCTREEWIN-5947] Checkbox missing for unstaged files

            Craig Smith added a comment - - edited

            I agree with Andreas.  This is a common issue with interface design.

            Very happy to see it back though.  I've been putting off upgrading from v1.7 mostly for this reason... and a couple of others I've forgotten about it's been so long.

            Craig Smith added a comment - - edited I agree with Andreas.  This is a common issue with interface design. Very happy to see it back though.  I've been putting off upgrading from v1.7 mostly for this reason... and a couple of others I've forgotten about it's been so long.

            amaly added a comment - - edited

            Thank you for the "+/-" buttons for staging and unstaging. That is already a huge improvement on the former checkboxes gone missing. 

            Not particularly wanting to be nitpicking, but having the "+/-" buttons to the left of the filename would be a huge improvement over having them on the right of the filename. Having the buttons right-aligned potentially (depending on screen size, window layout, ...) puts a lot of whitespace between the filename and the button, making it hard to associate the filename with the correct "+/-" button if you have a lot of changed files.

            amaly added a comment - - edited Thank you for the "+/-" buttons for staging and unstaging. That is already a huge improvement on the former checkboxes gone missing.  Not particularly wanting to be nitpicking, but having the "+/-" buttons to the left of the filename would be a huge improvement over having them on the right of the filename. Having the buttons right-aligned potentially (depending on screen size, window layout, ...) puts a lot of whitespace between the filename and the button, making it hard to associate the filename with the correct "+/-" button if you have a lot of changed files.

            3.0 includes stage/unstage "+/-" buttons.

            Mike Corsaro (Inactive) added a comment - 3.0 includes stage/unstage "+/-" buttons.

            So is this ever going to get fixed? Last I checked Sourcetree on MacOS still had the checkboxes and I use them ALL THE TIME.

            Unfortunately Sourcetree on my Windows machine does not have the checkboxes anymore.

            Please just bring back the checkboxes. Or at least provide the OPTION of using checkboxes. I know this was some sort of UX or design decision, but you should not just simply kill a feature that obviously many people used. At least provide the option to turn checkboxes back on.

            Jake Wilson added a comment - So is this ever going to get fixed? Last I checked Sourcetree on MacOS still had the checkboxes and I use them ALL THE TIME. Unfortunately Sourcetree on my Windows machine does not have the checkboxes anymore. Please just bring back the checkboxes. Or at least provide the OPTION of using checkboxes. I know this was some sort of UX or design decision, but you should not just simply kill a feature that obviously many people used. At least provide the option to turn checkboxes back on.

            lumenetix added a comment -

            wow... since when programers are allowed to remove features like this one without replacement?! That simply mean that the replacement for the, albeit awkward but useful feature, was not ready.

            Somebody approved this and should not have is or her donuts at the next Friday happy hour... 

            lumenetix added a comment - wow... since when programers are allowed to remove features like this one without replacement?! That simply mean that the replacement for the, albeit awkward but useful feature, was not ready. Somebody approved this and should not have is or her donuts at the next Friday happy hour... 

            Peter Hinz added a comment -

            Just bring back the old interface. It was working 100%

            Peter Hinz added a comment - Just bring back the old interface. It was working 100%

            Thanks Rahul! Either the old checkboxes or the proposed +/- buttons work for me, as long as it's something that allows staging files individually without a lot of mouse-work. I'm reverting to 1.8.3 for now, until the option is back (yes, for me, it is sufficiently irritating for smooth workflow). The checkboxes (or other) are still missing as of 1.9.10.0.

            Erik Blake added a comment - Thanks Rahul! Either the old checkboxes or the proposed +/- buttons work for me, as long as it's something that allows staging files individually without a lot of mouse-work. I'm reverting to 1.8.3 for now, until the option is back (yes, for me, it is sufficiently irritating for smooth workflow). The checkboxes (or other) are still missing as of 1.9.10.0.

            lukerayman added a comment -

            Thank you, Rahul, for making these changes. We used to use checkboxes even if it was a bad UX (checkbox is for selecting not for making immediate changes). Now it feels more properly. 

            lukerayman added a comment - Thank you, Rahul, for making these changes. We used to use checkboxes even if it was a bad UX (checkbox is for selecting not for making immediate changes). Now it feels more properly. 

            I personally am not a fan of the new screenshot.  The pluses and minuses make me think it will expand or minimize something.  Just seems weird to use a very common conventions in non standard ways. 

            Kevin Ashton added a comment - I personally am not a fan of the new screenshot.  The pluses and minuses make me think it will expand or minimize something.  Just seems weird to use a very common conventions in non standard ways. 

            Thank you for all the feedback. As some of you noted in your comments, the original experience was a bit awkward. We intend to bring the functionality back, but in a more appropriate user experience. Below is an example of what that might look like:

             

            We've been hard at work improving the infrastructure and performance of SourceTree for Windows. The most recent version, SourceTree for Windows 1.9.9.20 [1], includes a variety of bug fixes, Git LFS 1.5.2 support, patched memory leak, and performance improvements when switching tabs. Improving the overall user experience is next on the list. Thanks for your patience. 

            Lastly, if you'd like to chat about SourceTree and what we're working on, please feel free to grab some time on my calendar https://calendly.com/rchhabria/atlassian. You'll get sent an automated calendar invite with a Google Hangouts link for us to connect over. 

            [1]http://downloads.atlassian.com/software/sourcetree/windows/SourceTreeSetup_1.9.9.20.exe

            Rahul Chhabria (Inactive) added a comment - - edited Thank you for all the feedback. As some of you noted in your comments, the original experience was a bit awkward. We intend to bring the functionality back, but in a more appropriate user experience. Below is an example of what that might look like:   We've been hard at work improving the infrastructure and performance of SourceTree for Windows. The most recent version, SourceTree for Windows 1.9.9.20 [1] , includes a variety of bug fixes, Git LFS 1.5.2 support, patched memory leak, and performance improvements when switching tabs. Improving the overall user experience is next on the list. Thanks for your patience.  Lastly, if you'd like to chat about SourceTree and what we're working on, please feel free to grab some time on my calendar https://calendly.com/rchhabria/atlassian . You'll get sent an automated calendar invite with a Google Hangouts link for us to connect over.  [1] :  http://downloads.atlassian.com/software/sourcetree/windows/SourceTreeSetup_1.9.9.20.exe

              Unassigned Unassigned
              77be48e0e07e Jogchem Andre Oord
              Affected customers:
              44 This affects my team
              Watchers:
              51 Start watching this issue

                Created:
                Updated:
                Resolved: