Thanks everyone for your continued feedback, and your passion in lobbying for Mercurial support in what is now known as Bitbucket Server. Although we've been a bit quiet on this suggestion lately, your comments have not gone unnoticed.
Mercurial support is one of the more popular suggestions for Bitbucket Server. In considering whether to deliver Mercurial support in the near future, we have taken into account a number of factors and feedback here on this suggestion is an important indicator for us. Unfortunately we can't be all things to all people, so prioritisation has to come into play. Based on all the information available we have decided not to proceed in adding Mercurial support to Bitbucket Server at this time. Our teams are driven to deliver highly engaging and useful products for professional teams and when it comes to Bitbucket Server our focus has been on delivering a rock solid, highly scalable product that can be depended on with world class support.
Bitbucket Cloud's Git and Mercurial support continues to go from strength to strength. We have no plans for that support to cease. Although Bitbucket's primary messaging focuses on Git this should not be taken as an indication of our commitment to customers using Mercurial in the cloud. In fact, I'd very much recommend it to those wanting to host Mercurial repos and I'd love to hear of any barriers that prevent you from doing so.
We absolutely appreciate the votes and comments on this suggestion as it drives conversation and reflection about what we are delivering (more often that you might imagine, I suspect). I encourage you all to continue to vote and watch this suggestion and we will continue to monitor the DVCS market for developments. If anything changes, we'll be sure to note it here. If you would like to know more about how Atlassian Product Management uses customer input during the planning process, please see this post on Atlassian Answers and our new features policy.
Product Manager - Bitbucket