Distributed teams can now build faster with Bitbucket

By on January 21, 2016

Strong innovators have always aspired to be faster. Fast development cycles lead to more innovation and lower costs according to a recent survey on innovation by Boston Consulting Group. We at Atlassian are committed to helping teams deliver software at speed. Last September, we announced critical new capabilities to enable teams to do just that: build faster with Bitbucket. We’re excited to announce that these features are now available:

Smart Mirroring

Git Smart Mirroring

Many software teams using Git can build up large repositories over time due to a large amount of historical information, use of monolithic repositories, storage of large files, or a combination of the three. Developers working from remote locations need to wait hours when cloning, which is a big drain on productivity. Smart Mirroring can drastically improve read (clone, fetch, pull) performance for distributed teams working with large repositories by making them available from a nearby server. As an example, in one of our own internal tests, we have seen clone times get 25X faster for 5GB repositories between San Francisco and Sydney.

A mirror server is simple to configure, easy to maintain, and automatically uses existing authentication mechanisms. Unlike some other solutions available in the market, you don’t need to install or configure a whole new instance in order to create a mirror server, or mirror the repositories one at a time. Administrators will love how simple it is to host a mirror server, and developers will appreciate how the vastly improved clone and fetch times speed up their workflow.

Interested in learning more about Smart Mirroring? Register for the webinar, “Speed up distributed development with Smart Mirroring for Bitbucket Data Center” happening on March 3rd.

Git Large File Storage (LFS)

Git Large File Support | Git LFS

Modern software teams at their core consist of not just developers but designers, QA engineers, writers, and more. These teams track assets such as graphics, videos, and other binary files that are inherently large. Git’s original performance goals for distributed version control weren’t optimized for tracking large binary files, making it unsuitable for storing large assets. With the addition of Git LFS support, software teams can track all the assets they produce together in one single place and be productive at the same time. Large files are kept in parallel storage, and lightweight references are stored in your Git repository making your repositories smaller and faster.

Projects

Bitbucket Projects

As organizations grow, team sizes get bigger, and more and more repositories get added. It gets progressively harder to find the repository you’re looking for. Projects make it easier for teams to organize their repositories and become more productive with Bitbucket Cloud. This feature is already available in Bitbucket Server and Data Center. We also took this opportunity to refresh our UI in Bitbucket Cloud and make it easier for you to find what you’re looking for.

Get started with Bitbucket

With the addition of Smart Mirroring, Git LFS, and Projects – Bitbucket is now more suited than ever for professional teams. Organizations of all sizes – from large enterprises such as Verizon and Nordstrom to small startups like Pinger and Kaazing – are using Bitbucket today, and we’ve heard from many that they’ll be using these new features in the coming weeks.

“Many of our customers have distributed teams that have experienced pain around storing large binary files and cloning performance. Smart Mirroring and Git LFS are two huge game changers that will boost productivity for our clients using Bitbucket around the globe. We are excited to roll it out to all our customers.” – Zubin Irani, Chief Executive Officer, cPrime

“Our developers are spread all over the world, and Bitbucket helps them remain aligned as they build powerful solutions for our customers. We are very excited about Smart Mirroring in Bitbucket which will not only improve multi-site clone performance but will also increase developer productivity of distributed teams.” – Kurt Chase, Director of Release Engineering, Splunk

Our JIRA Cloud customers picked Bitbucket as their #1 Git solution. More than 1 in 3 Fortune 500 companies trust Bitbucket and are using it every day to innovate faster. If you’re new to Git, head over to “Getting Git Right.”

Or, if you’ve already made a decision to switch to Git, click the link below!

Try Bitbucket Free

  • ScottMcGready

    What the fresh hell is this? I don’t want this project crap, it was easy enough before. I wasn’t notified of the change and now it’s just happened. HOW THE HELL DO I SWITCH IT OFF!?

  • Mat

    Nice one!! Please fix pagination (doesn’t work properly with filters now). Thanks!

    • Alastair Wilkes

      Thanks for the feedback! We’re taking a look, but please contact support@bitbucket.org if you continue to have issues.

  • Mat

    Also choosing color of icon would be nice!!

    • punker

      Man, they just need to back good ol’ pics instead of shitty enterprisy icons.

  • John

    Projects are ok, but I hate alphabetically sorted repositories. I see 8 pages and I don’t know which projects are dead/updated. Before projects I saw when someone pushed code to repository. Also when I pushed code I just clicked on first repo in the list. With projects I need to find repository by name. That’s big disadvantage for me

    • dominik_h

      Agree. Please add option to sort by last used projects. Other changes looks nice. Good job!

    • Jens Schumacher

      Alphabetically sorted repositories are great for exploring a project, that’s why we’ve ordered them on the Dashboard in that way.

      However, to access recent projects and repositories, you can still use the drop-downs in the header.

      • Andrew Hall

        I agree with these guys – it would be really nice to see an option to sort by last modified date instead of alphabetically.

        • andrewlippert

          Not just ‘nice,’ essential. As a manager of an extended virtual team working on multiple projects simultaneously, being able to review the most recent work by my staff requires the sort to default to ‘last updated.’ Adding an option to sort alphabetically would be ‘nice.’ Not, the other way round. And a drop down menu listing the last 5 updated is a ridiculous response as a suggested alternative.

      • Burhan Khalid

        Hi Jens – did an actual developer tell you this? I’m being serious – because this sounds so much like a product manager / marketing blurb.

        No developer browses projects alphabetically. It is just so far out of field for how people use source control I can only assume this came from some product team and not from actual developers.

    • Codelegance

      Have you tried GitHub?

    • Soni L.

      Projects are nice, but I long for the day when we’ll get subprojects, in a tree structure, just like a modern file system.

  • Sergey

    Allowing to change permissions of the projects would also be nice

    • Alastair Wilkes

      Hi Sergey,

      Thanks for the feedback. Right now, you can change from private to public projects. Find out how in our docs: https://confluence.atlassian.com/display/BITBUCKET/Projects

      Other than that – we do plan to add permissions to projects, but we don’t have an ETA at this time. Thanks!

      Alastair Wilkes

      Bitbucket Product Manager

      • andrewlippert

        We inadvertently had a public repo in our intentionally private account. The default project created at launch of this feature is consequently PUBLIC? All of our other repos are private. Changing the permissions on the errant repo does not permit me to switch my default project to private?! Seriously?

        • Alastair Wilkes

          If you’ve changed the previously public repo to private, you should be able to modify the project setting to private as well. However, you also cannot have a public issue tracker or wiki in private projects, so that might also be preventing the change – can you check the issue tracker and wiki settings on that repo to see if that’s the issue? If the issue persists, please reach out to support@bitbucket.org so we can help further. Thanks!

          • andrewlippert

            Repos all show private. Previously public repos have no issue tracker or wiki associated. Yet, project settings still preclude a switch to private. How do you determine which object offends? All repos in our account show as private right now, but I am not going to go through 80+ repos to find which might have offended this feature’s sensibilities. Poorly executed, me thinks.

          • Alastair Wilkes

            Thanks for checking on that setting! Sorry you’re still experiencing issues – shoot us an email to support@bitbucket.org and we’ll get it sorted out.

  • Cleiton Alves

    We lose all project icons. =[

    • John

      You’re right. I wonder who thought that repository icon isn’t needed. I don’t see it in settings, so I guess that it was removed. Such a shame. It’s easier to remember icon than name of repo.

    • william.mcbroom@oc.edu

      I miss the repository icons too.

    • andrewpey

      Oh bitbucket, what have you done…

    • boriel

      Same here. I really miss then :(((

    • ijcaluscusan

      The project icons now set the icon of the repository. I lost all too. Painful transition, but it’s a good move.

      • Gonçalo Lopes

        I completely disagree that this is a good move!

        Actually, I don’t see any rationale at all for this, especially if the individual repository icons were already working. Even for repositories that are grouped under the same project you may want to see individual variants of a common logo to identify the different repos.

        It seems like bitbucket decided to violate the old maxim “If it ain’t broken, don’t fix it”.

  • Alessandro Tegner

    Whatever feature.

    We are eternally waiting for a search code.

  • Mustermann

    I want the old dashboard back! :'(

  • Ellery McKenzie

    WHERE THE HELL HAVE MY REPO ICONS GONE ?!?!?!?!?!?!?!?!?!

    I am one of those nice visual people who looks for repo by icon, not by name.

    Thanks for unnecessarily complicating things for me

    • andrewlippert

      Again – what were you thinking, mates?! You have deleted user data by removing repository icons. Totally boneheaded move, Drongo. Restore, restore, restore….

      • Gonçalo Lopes

        Actually, the original repository icons are still available at: https://bitbucket.org///avatar/

        But yeah, I agree this was a crazy move, no idea what the hell they were thinking!

    • andrewpey

      Same here 🙁

    • http://danilorechi.net Danilo Rechi

      Same here :/

  • Frank

    This projects thing is pretty crap tbh. Did anyone want it? Repo’s are containers, projects are items in a container. Where do teams fit into this weird new heirarchy?

  • Gabriel Villoldo

    Untitled Projects everywhere (you could pick up the owner’s name instead of a generic title) & the same icon for all projects. Please add different generic icons.

  • Patrick G

    The green icon is just plain ugly. OK, I stop trolling (it’s true anyway). But I would prefer not to be forced to include all my repos into a default untitled project. I would like to have repos not attached to any project. I cannot do it right now. Or have a repo attached to more than one project. This happens so often. Also, I liked the fact that I could see when the last commit was (x minutes ago) without actually having to go in the repository. This is gone too. And btw, why can’t I use my bitbucket login to comment in here???

    • Franklin Yu

      “Or have a repo attached to more than one project.” It’s not “project” feature; it’s called tags, a feature not yet released.

  • Josh Santangelo

    How do you switch on git-lfs? I don’t see a setting for it. Or is it just magic?

  • http://forerunnergames.com/ Aaron Mahan

    I can’t stand the projects feature. It’s forced upon me with no way to turn it off. For me, a respository IS A project. I’m sure this worked for someone having hundreds of repositories somewhere, but what about small accounts that may only have 1 or several repositories? It makes no sense. What’s worse, I can’t remove the repository from this new “Untitled Project” that was created for me, that I didn’t want.

    • https://plus.google.com/+JasonMaggiacomo Jason

      Welcome to the Internet of Things; where your choices have been decided for you.

    • Soni L.

      Think about it like your filesystem. Do you put EVERYTHING IN THE ROOT PARTITION?! Wait some ppl actually do that…

    • jon

      Projects should be an optional add on feature. It is really irritating

  • Josh Santangelo

    Projects are cool, but the default, unremovable, untitled one isn’t. I just renamed it to “All” which makes it at least less annoying.

    • Reece Hart

      Agreed. Projects is a great *optional* feature, and a terrible one to foist on users. Should have been opt-in.

  • Gleb Pitsevich

    Guys, this is just crazy…

    This update turned my dashboard into a huge piece of shit.

    How should our team of 30+ people get to work tomorrow? I spent 10 minutes in the dashboard, and it still looks weird to me.
    How can I still get sense of how 100+ projects are going on, if you decide to sort them ALPHABETICALLY???

    APLHABETICALLY!!!
    What is that shit?
    You addressed a feature request from people who name the projects – projectA,projectB,projectC, projectD???

    “To help you get started, we created an UNTITLED PROJECT for each team’s repositories.”

    UNTITLED PROJECT!!!!!
    Holy shit – how many people thought it’s a great idea??

    How come you do such a big updates, without notifying people in advance about your intentions???

    How come you don’t make them optional???

    Rollback this shit, think about it – and if you still sure that it’s good updates, then notify people 2 weeks ahead and give everyone time to switch to Github..

    • Miguel Dario Ferrer

      Agreed, what happened with repository icon? WTH.

  • Reece Hart

    Please make projects optional per repo. Forcing this new view on folks is uncool.

    Also, projects is way lower in priority than code search in my opinion. Please take care to listen to users. I have yet to see a user write “Great. This solved my problem.”. You don’t get credit for solving non-issues.

    • Konato_K

      Projects are only for Team repositories, if you have a repository on your account (not a team) then you don’t have a Project (you can’t have it, even if you want)

  • Michael Scarchilli

    Not even 24 hours and the pitch forks are out!

    Bring back the ability to order by push date, and bring back our icons!
    ..

  • Patrick G

    please make projects optional, bring back repos sortable by last modification. or simply rollback the change.

  • pzelnip

    On this change all my repos for the team ended up as a single project. Upon going to my team page and clicking “Projects” I see no way of adding a new project.

    It took me a good 5 minutes before I noticed that “Create project” was on the Projects dropdown in the top navbar.

    • pzelnip

      For that matter, how do you move a repo from one project to another?

      • http://about.me/chris.charabaruk Chris Charabaruk

        Easy as adding it to the other project.

        • pzelnip

          Ahh, I see. I would’ve thought that it would’ve been done from the repo itself, and not the project.

  • http://facespace.com FaceSpace

    I can search my code now????

  • http://seomention.com Steven Britton

    Isn’t a repo a project? This seems like an unnecessary layer of grouping. One suggestion – maybe default the icon back to its original icon if a project icon doesn’t exist.

  • Prem Radhakrishnan

    What mostly everyone is saying on this blog post. This completely SUCKS, I cannot see the most recently modified repo and I manage different teams working on different things.

    The dashboard is a big pile without providing any useful information other than a list of repositories and all under “Untitled Project” , I mean like someone else commented who thought of that ? I had a lot of respect for the bitbucket team but I think you guys are victims of some kind of corporate sabotage and someone is out to get you coz this change is not pleasing people .. I thought it might just be me not liking change but then I realized by reading the comments that most people who are lamenting have the same frustrations as me

    Theres my 2c !

    • andrewlippert

      Alastair Wilkes or mindsocket- Would love to see one of the Bitbucket Product Managers respond to these issues. Your customers expect more. You have deleted customer data, imposed inappropriate organizational structures, and cost your paying customers substantial productivity without any option of restoring previous capabilities. Silence, in this case, is NOT a virtue.

      • Jens Schumacher

        Hi Andrew,

        We didn’t delete customer data, we merely don’t have a place in the UI to display it any longer. Considering projects, or a way to organise repositories, has been the 3rd most voted for feature for Bitbucket, I would also argue that it’s not an inappropriate structure.

        That being said, I will respond with a more detailed comment outlining some of the reasons behind the decisions we’ve made.

        • andrewlippert

          No. Part of the data related to my repositories were the icons selected, designed and associated with each. These icons enabled a visual distinction between the repositories and provided another mechanism for organizing and referencing the data. That information is now gone – you have deleted the data which I had entered into the system. In your current design, each repository still has an associated icon in the dashboard. That icon ought be the one I originally associated with the repository – the data I had entered into the system. Restoring that data should be a central concern to you and your team.

          Being unable to reference my repositories by last update is a significant functional regression that directly impacts my team’s productivity. There is simply no reason an alphabetical organization as the exclusive ordering makes any practical sense at all. As an additional, optional ordering, I can understand the appeal. But, I consider the imposition of the alpha sort a significant problem with this release.

          I certainly did not vote for an imposed organizational structure for my repositories. I strongly suspect _none_ of your customers requested that you deploy something that required their repositories be placed in a ‘project.’ You have deployed a solution (imposed your decision) with no option for me, or other paying customers, to elect a different approach. That, is inappropriate. For any customer with a single repository, adding in an additional organizational layer in the form of ‘projects’ is superfluous and inappropriate. This ought be an organizational enhancement optionally implemented by individual customers, not a blanket approach required of all users.

          You have directly impacted my productivity and the productivity of my team with no notice and no ability to counter your decisions. If you had approached this as an optional enhancement to functionality already in place, we’d be having a different conversation. I am quite disappointed you feel justified in imposing this approach on unsuspecting customers.

        • Ganey

          “Considering projects, or a way to organise repositories, has been the 3rd most voted for feature for Bitbucket”

          Judging by the other comments here, ordering by modified will now become the most voted feature for Bitbucket

        • punker

          I think removing user data (repo icons) is not good idea to bring up ‘cool upvoted feature’. However, if this weird was on 3rd place, what is 1st and 2nd most upvoted features?

        • Patrick G

          It may be the 3rd most voted feature. But you definitely have chosen the worst way to implement it.

        • Prem Radhakrishnan

          If you have not deleted customer data then why did you replace it with folder icons ? and in some cases you replaced it with the picture of the owner of the repo from the passport authentication via google+ etc.

          I dont know why you cant see that your customers are outraged by the decisions you have made, if your goal was to drive users away you have succeeded.

          Suppose you have sticky markers of different colors in a book that you were reading each signifying something, and one day you woke up to find all of them replaced by the same color marker how would you feel about it ?
          And then your library that was organized chronologically was all of a sudden put into one shelf in alphabetical order on top of that ?

          Think about how you are impacting productivity for customers before you respond to comments

  • Maxim

    I’ve lost all the custom icons previously assigned to all my repositories. Please get them back.

    • andrewlippert

      Customer data deletion. Not appreciated.

  • Noon

    instead of a repo having a single “project” you should definitely just have repos having “tags”. then all of it is totally opt in, *and* we should give repos more than one tag (a feature that would be useful at our workplace).

    tags over projects!

    otherwise, i’m excited about the git LFS changes! nice one!

    • Iain Hunter

      +1 for tags over projects

  • seenu

    what the fucking shit is this….

    you force your ideas on us without even giving an option?

    still i wanted to make use of it and started to make use of your projects features and get this error

    http://www.clipular.com/c/4865388421054464.png?k=3prdlPVd2-ikpSh-dC8GDbswSZ8

  • seenu

    for everyone having hard time to see recently updated repos,

    click on teams in top menu and select a team then you can see updated repos on top

    PS: if you choose different project names for your repos then you are fucked up again

  • Will T

    C’mon on guys, can we please bring the old dashboard back?

    Sorry for being harsh, but the new dashboard is a joke, sorting projects alphabetically and only showing last 5 “viewed” projects, I am starting wondering that if product owners from bitbucket.org are actually using this project on daily basis.

    We want this project stays as simple and intuitive as possible, that’s it!

  • gskema

    Any instructions on how to connect JIRA projects with the BitBucket projects ?

  • Olek

    I wonder what is the limit for git lfs?

  • Adam Ainsworth

    Sounds like someone from Marketing got involved and decided they know what’s best for the devs.

    This changes are unhelpful at best, and if you want your paying customers to hang around, I would suggest rolling back the updates, and consulting with us first.

    • Patrick G

      +1

  • ted

    where are my icons?
    why do all repos have to be in a project?
    why is it not possible to sort by the updated date?

    please bring back these options. Thanks.

  • Iain Hunter

    +1 on sort by last updated. Can see this is useful for large organisations, but feels clunky for small teams which (as I do) map a repo to a project 1:1

  • Herman Yanush

    Please make projects for users and get icons back

  • Motiejus Vilmantas Bagdonas

    Sounds good, but where did project icons go???!!! We spent hours to upload customers logos so it’s easier to navigate, now they all look the same. Not cool. :///

  • Hans Spooren

    Please include last-updated timestamp back in overview.

  • xuhx

    Project icons gone. All repositories forced into an “Untitled Project” whether we wanted and/or needed them to or not. Some of us can’t create projects; no “Create Projects” option on the top-bar drop-down menu. The far-left ‘menu’ icon that should allow navigation to other Atlassian stuff (Jira and Confluence in our case) is broken; all options greyed out and suggesting we “Connect Bitbucket with other great Atlassian products” … which we already had and which works from the other products.
    Did anyone actually test this before release? We are so unimpressed.
    And Jens Shumacher, telling us “We didn’t delete customer data, we merely don’t have a place in the UI to display it any longer” is massively disengenous; you *have* deleted the project icons and I see little reason they couldn’t stay exactly where they were for a rep not in a project (which could/should be an option).

  • zdm

    1. restore repositories icons;
    2. add various sorting in dashboard;
    3. remove “recently viewed” – this is stupid and unusable piece of shit, or move it somewhere from center of the dashboard;
    4. kick your project managers asses;
    5. do all this things ASAP;

  • James Vanns

    Please revert to most-recently modified repos on the dashboard page or at the very least provide us end-users with the option to do this. Don’t even get me started with the icons! Visually, this is is a piece of shit – it really doesn’t provide a better user experience, either.

  • Thomas Sondergaard

    Smart Mirroring for cloud would be fantastic. Can we expect to see that soon? It should also help reduce the load on your servers, I should think!

    • Raj Sarkar

      We are working on it Thomas 🙂

  • https://plus.google.com/+JasonMaggiacomo Jason

    The real problem here is that all this fuss over what has changed could have been resolved before it began, by providing your customers with a preview of the upcoming changes, and gathering feedback then before it went live. After the recent change from Jira to Jira Software, I’m surprised Atlassian didn’t learn this lesson from that experience.

  • markbr

    I think this is very interesting. However, is there an way back to restore my project icons?

  • Jens Schumacher

    Introducing projects to Bitbucket was no trivial task. Inserting a new container into a system is a high impact change that touches almost every screen and interaction in one way or another. Guided by Bitbucket Server, where projects existed since day one, we’ve spend the last few months looking into the best way to bring this feature to Bitbucket.org.

    Is what we came up with perfect for everyone? No, but if you aim to build something that works for everyone, it often ends up working for no one. For better or worse, we had to make some decisions that we know would be controversial, but hopefully I can provide some more context around some of the issues that have been mentioned in this post.

    ### Mandatory projects

    Projects are an integral part of how teams work in Bitbucket Server, and was a highly requested feature from users looking for better ways to organise their repositories.

    While a highly requested feature, we also understood it would add overhead for individuals who only maintain a couple of repositories. Therefore we introduced Projects as a Team only feature.

    Our goal for Projects in Bitbucket was to add an additional layer of structure without introducing navigational overhead. From the Dashboard you can still access your repository directly. Recently accessed repositories sit at the top of the list and can be accessed from anywhere via the global navigation bar. If you are a member of multiple teams or have a number of projects, you can now filter the list of repositories by owner and project name.

    ### Repository avatars

    We had a long internal discussion on whether we should continue to support repository avatars. We know that a number of users spend time crafting custom repository avatars to identify their projects, but we also knew that only a very small percentage of our users actually used the feature.

    With the introduction of projects, it was more natural to move the avatar from the repository level up to the project level. More and more projects are composed of multiple micro services or modular architectures and therefore have many repositories. Coming up with a single avatar representing the project rather than one for each repository within the project seemed like a more scalable solution.

    We acknowledge that some projects only have a single repository. For those cases we aimed to keep the overhead of having to create a project as simple as possible and ensure they don’t get in the way on a day to day basis.

    To be clear, we did not delete any data. Repository avatars are still accessible unter the following URL if you would like to retrieve them and upload them to your projects instead:

    https://bitbucket.org/%5Bowner%5D/%5Bslug%5D/avatar

    ### Alphabetically ordered repositories

    Alphabetical ordering is great for exploring and finding new repositories. However, it is still easy to access recent projects and repositories via the dashboard and the global navigation drop-downs.

    That being said, we acknoledge that we’ve lost the last updated time with this change, which provided a good indicator on whether a repository was active or not.

    We will continue to iterate and improve projects over the next few weeks and hopefully address some of the feedback we’ve received.

    We know this has been a big change and change can be frustrating. But we hope you’ll take a moment, give your new project a name and avatar, and start organizing your repositories. We think you will like it.

  • Jens Schumacher

    Introducing projects to Bitbucket was no trivial task. Inserting a new container into a system is a high impact change that touches almost every screen and interaction in one way or another. Guided by Bitbucket Server, where projects existed since day one, we’ve spend the last few months looking into the best way to bring this feature to Bitbucket.org.

    Is what we came up with perfect for everyone? No, but if you aim to build something that works for everyone, it often ends up working for no one. For better or worse, we had to make some decisions that we know would be controversial, but hopefully I can provide some more context around some of the issues that have been mentioned in this post.

    ### Mandatory projects

    Projects are an integral part of how teams work in Bitbucket Server, and was a highly requested feature from users looking for better ways to organise their repositories.

    While a highly requested feature, we also understood it would add overhead for individuals who only maintain a couple of repositories. Therefore we introduced Projects as a Team only feature.

    Our goal for Projects in Bitbucket was to add an additional layer of structure without introducing navigational overhead. From the Dashboard you can still access your repository directly. Recently accessed repositories sit at the top of the list and can be accessed from anywhere via the global navigation bar. If you are a member of multiple teams or have a number of projects, you can now filter the list of repositories by owner and project name.

    ### Repository avatars

    We had a long internal discussion on whether we should continue to support repository avatars. We know that a number of users spend time crafting custom repository avatars to identify their projects, but we also knew that only a very small percentage of our users actually used the feature.

    With the introduction of projects, it was more natural to move the avatar from the repository level up to the project level. More and more projects are composed of multiple micro services or modular architectures and therefore have many repositories. Coming up with a single avatar representing the project rather than one for each repository within the project seemed like a more scalable solution.

    We acknowledge that some projects only have a single repository. For those cases we aimed to keep the overhead of having to create a project as simple as possible and ensure they don’t get in the way on a day to day basis.

    To be clear, we did not delete any data. Repository avatars are still accessible unter the following URL if you would like to retrieve them and upload them to your projects instead:

    https://bitbucket.org/%5Bowner%5D/%5Bslug%5D/avatar

    ### Alphabetically ordered repositories

    Alphabetical ordering is great for exploring and finding new repositories. However, it is still easy to access recent projects and repositories via the dashboard and the global navigation drop-downs.

    That being said, we acknoledge that we’ve lost the last updated time with this change, which provided a good indicator on whether a repository was active or not.

    We will continue to iterate and improve projects over the next few weeks and hopefully address some of the feedback we’ve received.

    We know this has been a big change and change can be frustrating. But we hope you’ll take a moment, give your new project a name and avatar, and start organizing your repositories. We think you will like it.

  • Jens Schumacher

    Introducing projects to Bitbucket was no trivial task. Inserting a new container into a system is a high impact change that touches almost every screen and interaction in one way or another. Guided by Bitbucket Server, where projects existed since day one, we’ve spend the last few months looking into the best way to bring this feature to Bitbucket.org.

    Is what we came up with perfect for everyone? No, but if you aim to build something that works for everyone, it often ends up working for no one. For better or worse, we had to make some decisions that we know would be controversial, but hopefully I can provide some more context around some of the issues that have been mentioned in this post.

    ### Mandatory projects

    Projects are an integral part of how teams work in Bitbucket Server, and was a highly requested feature from users looking for better ways to organise their repositories.

    While a highly requested feature, we also understood it would add overhead for individuals who only maintain a couple of repositories. Therefore we introduced Projects as a Team only feature.

    Our goal for Projects in Bitbucket was to add an additional layer of structure without introducing navigational overhead. From the Dashboard you can still access your repository directly. Recently accessed repositories sit at the top of the list and can be accessed from anywhere via the global navigation bar. If you are a member of multiple teams or have a number of projects, you can now filter the list of repositories by owner and project name.

    ### Repository avatars

    We had a long internal discussion on whether we should continue to support repository avatars. We know that a number of users spend time crafting custom repository avatars to identify their projects, but we also knew that only a very small percentage of our users actually used the feature.

    With the introduction of projects, it was more natural to move the avatar from the repository level up to the project level. More and more projects are composed of multiple micro services or modular architectures and therefore have many repositories. Coming up with a single avatar representing the project rather than one for each repository within the project seemed like a more scalable solution.

    We acknowledge that some projects only have a single repository. For those cases we aimed to keep the overhead of having to create a project as simple as possible and ensure they don’t get in the way on a day to day basis.

    To be clear, we did not delete any data. Repository avatars are still accessible unter the following URL if you would like to retrieve them and upload them to your projects instead:

    https://bitbucket.org/%5Bowner%5D/%5Bslug%5D/avatar

    ### Alphabetically ordered repositories

    Alphabetical ordering is great for exploring and finding new repositories. However, it is still easy to access recent projects and repositories via the dashboard and the global navigation drop-downs.

    That being said, we acknoledge that we’ve lost the last updated time with this change, which provided a good indicator on whether a repository was active or not.

    We will continue to iterate and improve projects over the next few weeks and hopefully address some of the feedback we’ve received.

    We know this has been a big change and change can be frustrating. But we hope you’ll take a moment, give your new project a name and avatar, and start organizing your repositories. We think you will like it.

    • Patrick G

      Thank you Jens for the insights and providing the reasons for such a dramatic change. I still think Projects should be optional.

      • John

        Required projects are not a problem. I really don’t get argument about alphabetical ordering:

        > Alphabetical ordering is great for exploring and finding new repositories.
        > Alphabetically sorted repositories are great for exploring a project, that’s why we’ve ordered them on the Dashboard in that way.

        That’s like argument from commercials. I guess I am not a target audience for Bitbucket. Active developer doesn’t spend 80% time by exploring and finding new repositories (or recently viewed). I see hundreds of repositories from multiple teams and right now I am really confused. Let’s hope it will get better in next weeks, otherwise it’s time to move on.

    • AmericanHoser

      No one’s upset about you adding project support to Bitbucket. It’s a feature that’s very useful and has its place. However, the way you implemented it is a bit silly. Every repository now has to be in a project (default “Untitled Project”). But apparently, that’s only for teams – individual users still have their repos outside of a project. So we know they don’t *have* to be in projects – you just forced it to be that way. Accounts either have a mandatory 1-level organization (individual users with individual repos) or a mandatory 2-level organization (team users with all repos forced inside projects). It’s not an optional feature to simplify people’s lives, but a forced requirement under certain circumstances. It’s obvious how hard-coded this is.

      This is not an impressive implementation.

      Not only that, but it’s not that hard to have icons (not “avatars”, since those traditionally represent cognizant beings, not data locations) at the project and at the repo level. The repo icon (if set) would always show. Otherwise the project avatar (if set) would show. We also use the at least moderately useful code language-based default icons in favor of your silly colored folders. Which is also a silly default icon because you expect folder icons to be containers, yet you use it for each item in the container.

      If you’d made the default view a tree view, then we’d only see the project icon at the top of the tree and we’d still see the individual repository icons beneath it. That would have been great – we’d be able to view and organize multiple repos with their own icons under project icons. The project icons would be collapsable and it’d be vastly easier to navigate. All repos with unset projects would be displayed under a “No Project” group. That would encourage people to set projects on their own to take advantage of the tree sorting.

      But no, you gave us this. Pages and pages of the same icon, alphabetically sorted. Good job. Pat yourselves on the back, and tell yourselves it’s just because we don’t understand.

    • Noon

      remove projects and implement tags! then life will be great. now, not so great.

    • Peter

      “However, it is still easy to access recent projects and repositories via the dashboard and the global navigation drop-downs.”

      After pushing new code to team’s repository I don’t see repo in recently updated menu 🙁

    • Burhan Khalid

      If it was limited to Bitbucket Server, surely you could have made it optional for those clients and not everyone else that uses bitbucket.org (for the record, I am also a bitbucket server user and I most definitely didn’t ask for projects).

    • jon

      Projects should an optional add on. Otherwise it imposes a lot of work on those that don’t want it.

    • xuhx

      “To be clear, we did not delete any data. Repository avatars are still accessible […]”
      Fair enough, they weren’t outright deleted … though I’d note ‘hidden’ is functionally the same as ‘deleted’ to an end-user, and it is a mystery to me how we would have found them without finding your post above. Also icons, not avatars.

      “With the introduction of projects, it was more natural to move the avatar from the repository level up to the project level.”
      How? If they’re used on a per-repository basis, for repositories that may have very different contents however linked at Project level, they will likely need per-repository icons. Project-level makes them near useless, unless you have few-to-one repositories per Project. Project level could/should have its own separate icon. Maybe used as the default for associated repositories until a separate one is selected, but unless they can be set per-repository they can’t provide their useful function of an easy visualisation of the repository type.

    • Ganey

      In 3 day’s I’ve had 60 votes on ‘restoring last modified to dashboard’, bear in mind users have been putting in issue requests for sortable dashboard items over the years since 2013 see #6899 as a starting point (might go back earlier).

      Recently accessed gets filled when a project that uses several repositories gets updates, so a list of 5 or so isn’t the greatest of use there.

      It took me about 3 hours to write the old dashboard into an add-on (with sortable columns) using the API and now I’m just going through the lengthy process of submitting the add-on for others to use.

    • Jean-François Héon

      I really like the projects feature. In fact, I had been creating dummy teams of one user in order to group repos together. In my case, it would be great to be able to create projects for my individual user instead of creating dummy teams. I guess meanwhile, I can create a “Projects” team and put all my projects there.

    • Marcelo Cantos

      Project avatars make perfect sense. Where you went wrong was in thinking that repo avatars therefore don’t make sense. Why couldn’t you just offer them at both levels? It probably cost more to remove repo avatars than to leave them there.

  • Jozef Repáň

    Thanks for this!

  • wpostma

    Why are all my project icons showing my user avatar instead of the bitbucket language default icon or my custom icon?

  • Daniel

    OMG, What did you do?! Where is the recently updated view? Please bring it back to the dashboard!

  • Damir Franusic

    I am getting tired of you BitBucket guys with your “great” ideas. I am now looking for an alternative and you have just lost one previously satisifed customer. I’m sure there’ll be more to follow. You really pissed me off when I logged in today and saw all my repo icons missing. I can only assume that similar fuckups will continue to happen and I am not willing to lose my time on your nonsense.

  • http://mpen.ca Mark P

    Please bring back the repo icons 🙁 On the team page you have two columns — one for Repository and one for Project. Just put the Repository icon next to the repository name and the project icon next to the project name. And then when I open a repo, put the *repo* icon in the top left. If you want to get all fancy you can put a smaller bubble to the to the bottom right with the project icon.

  • Aurélien Da Campo

    To be honest, I don’t like your new dashboard. I expected something better (like GitHub – a detailed history page on what’s going on) and we all get something worse… Sorry guys but when I see the good quality products of Atlassian, I sometimes wander if bitbucket is really made by Atlassian.. And by the way, we are still waiting for tab size in user preferences…

  • Roger @Getnoticed

    Thanx for changing my development environment on a monday-morning. Very professionel……

  • Jim

    The change might have gone better if you had made a project for each repository and migrated the avatar from the repository to the project. Then most people could have just ignored the extra column with the project. There would still be complaints due to the sorting change, but you will get some complaints for every change.

  • disqus505

    Once again, website designers that are not software developers have rolled out another highly disruptive and poorly thought-out update. JFC, what is wrong with the people at Atlasian?

  • James

    Some more information on LFS would be nice.

    It doesn’t appear to currently work with 2FA enabled accounts. Attempting to push against a repo prompts me for HTTPS password despite having the proper SSH keys setup.

    • Raj Sarkar

      Hi James,

      LFS is only available in Bitbucket Server and not Cloud.

  • Momo

    Projects are great! But how can I use my JIRA Cloud Projects? Don’t want to manage them twice.

  • Luke Hopkins

    Wow.. looking at some of these comments you’d think Atlassian literally killed some of these people kids…

    Don’t get me wrong, there are some obvious problems with the update and it definitely should have been beta’d for feedback.

    Either rename your “Untitle Project” to “All” or go through and create projects (it’s quick and easy, just did about 100 repos in 15 minutes). Upload your icons to the projects. Dashboard is more of an issue, but I’m sure based on the comments here they’ll resolve this as a priority.

    • Franklin Yu

      I personally don’t think the new features are that horrible; at least not “like junk” or “just a joke”. I can see that Atlassian team is trying to improve. Maybe the name of the feature “project” is causing some misleading; they may have called it “folder” as well. The “Untitled Project” may also be “stand alone projects” or something less misleading. Well the ordering is indeed sort of weird.

      • Luke Hopkins

        Yea exactly, sometimes I feel bad at the backlash companies recieve for any updates to their software. Your not going to please everyone and there are clearly a few things that Atlassian need to rework/rethink, but some of the responses on here are a bit extreme.

  • David Villa Alises

    An per-project issue tracker could be very interesting. Issues involving several repositories is very common in our organization.

  • Franklin Yu

    I guess most users do not know about the issue tracker for the site. It could be better to mass e-mail all the users about the planned change before actually applying them.

    I am happy with the feature, but I guess not everybody is.

  • Simon East

    Please vote for the issue here if you would like to get the last-updated-date ordering back:
    https://bitbucket.org/site/master/issues/12257/sort-dashboard-repositories-by-last

  • notrichnow

    Projects are cool. The new UI threw me for a loop at first, but we have lots of repos, that need better organization and this helps. It’s an extra step, but I can live with it. The one thing I am upset about is the “Create” button at the top. Adding the extra clicks to create something new, is annoying. Get it aligned with JIRA and Confluence, and I’ll be a happy camper!

  • Patrick G

    For those who would like to have Projects optional, please vote at:

    https://bitbucket.org/site/master/issues/12309/projects-should-be-optional

  • Colin

    Alphabetically sorted is a disaster. Please revert to (or add option to revert to) sorting by last used repositories.

  • Bruce Baker

    as discussed – preferred the previous version which showed last modified date/time

  • pedro

    like project organization, just is a little stretch, was good for me to organize repositories by business area for the company i work for, but with my personal repositories seems a little weird, i miss project logos too 🙁
    now is a little confusing but i think changes were good

  • bebo

    please bitbucket/atlassian .. restore that icons 🙁

  • Pierre Dumuid

    Did we lose the “repositories ordered by most recently committed to” list? I recall seeing this on the home page, and getting an immediate view on what our team had modified.

  • Raj Sarkar

    We have provided an update for Projects here which will answer most of your questions: http://blog.bitbucket.org/2016/02/24/new-improvements-for-bitbucket-cloud-projects/

  • Abhinav Gujjar

    I genuinely tried to use the projects “feature” but cannot figure out how this could be useful to me.

    I got a little excited thinking that project may let me manage bugs across several repos – but no. Well, then can I control permissions at a project level ? NO.

    This makes no sense at all.