HN Explorer

SourceTree 2.2 forces users to sign in to an Atlassian account

10 points by aaronbrager ↗ HN
Version 2.2 of SourceTree was released yesterday and it is impossible to use without creating and signing in to an Atlassian account.

If you think this is pointless and annoying, please upvote this issue: https://jira.atlassian.com/browse/SRCTREE-3452

If you want to download older versions they are here (for now)

http://downloads.atlassian.com/software/sourcetree/SourceTree_2.1.dmg

https://downloads.atlassian.com/software/sourcetree/windows/SourceTreeSetup_1.7.0.32509.exe

I'm not sure if the Windows version has the same annoyances or not

8 comments

[ 4.7 ms ] story [ 29.6 ms ] thread
joshschreuder
The Windows version added the same in 1.8 which was just released.

I'm not sure what the fuss is, a company provides a (quite good) tool for free, but require registration. This is done through their account system. What's the big deal?

aaronbrager
The mandatory registration is a little annoying, but fine. But the login flow is very disruptive and 100% blocking.
joshschreuder
They've always required you to register on their website and put a licence key in though.
daiearth22
For the same reason, I will suspend to use SourceTree for the moment. Not annoying but it is inconvenient. Hope Atlassian will fix it ASAP.
RealMarty
If it needs an account it's not free anymore. Goodbye SourceTree.
ksherlock
When I first installed SourceTree, back in March of 2013, it required an Atlasssian account.
aaronbrager
It required you download a license file from their website. It never required a disruptive (and buggy) mandatory in-app login until now.
jschulenklopper
> I'm not sure if the Windows version has the same annoyances or not

The OSX version has the annoyance that it will not startup at all. Navigation to the Atlassian site to enter the account data does not work, and in-application authorization needs to be done via an all-white form. The application is not usable anymore, and I downgraded to an earlier version.

Logged an issue, and Atlassian is working on it (and on almost 15 other issues registered on this version, as mentioned in the mail from Jira).