Hey, Kelvin from Atlassian here. We are pretty flat out ourselves improving both Bitbucket Cloud and Server. I can see how SSO isn't terribly important if Bitbucket is the only one of our products you use, but it's critical for our customers who co-own Bitbucket and JIRA (or Confluence, or HipChat, etc.). It was a fairly massive undertaking: retrofitting auth across our portfolio of products took some serious engineering effort. But we've still managed to squeeze a few fairly large releases out recently shipping features such as smart mirroring, Git LFS, and clustering - and have some other great stuff in the pipeline.

Hi Kelvin,

Any chance BitBucket has a public roadmap? I'm a user because of your free private repos, I hope to grow into a paid user this year. Thanks for all that you do!

Great to hear! Not quite, but we try to keep relevant feature requests on jira.atlassian.com (for Server) and https://bitbucket.org/site/master/issues (for Cloud) as up to date with progress as we can.

Honestly, I don't know why you didn't have SSO years and years ago. You encourage crosslinking between products that have distinct session lifetimes, I feel like I spend all day typing in my password again.

(Also, can you take the fucking 'remember me on this machine' button away? It's a cruel, cruel tease. It has not worked a single time on 4 different installations I've had accounts on over the years)

Did LFS support ship just for self-hosted? I was searching for a home for a few private repos days ago and #11204 showed LFS as still unsupported for hosted BitBucket.

https://bitbucket.org/site/master/issues/11204/support-git-l...

Yup, self-hosted for now but we're working to bring support for hosted soon.