Bitbucket Server 5.8 release notes
15 February 2018
Interested in trying a shiny new version? Don't forget to renew your active software maintenance! Renew now.
If you are upgrading from an earlier version, refer to the Bitbucket Server upgrade guide.
The Bitbucket 5.8 changelog is at the bottom of this page.
We love updates to search
Just in time to miss Valentines Day completely, Bitbucket Server has found an area that could use a little love. We've been working hard to refine search functionality across the product, and the release of 5.8 signals the beginning of something beautiful. First over the line? Global commit hash search.
Global commit hash search
Commit hashes in Jira, Bitbucket and Bamboo are linked to Bitbucket's commit view, making it easy to see the commit message and code diff for any change. When another tool gives you a commit hash, it's been hard to navigate to the commit view.
With the updated commit search, you can now paste the commit hash into the quick search box and jump straight to the commit view. It saves loads of time and helps your team understand the full context around a change.
Bitbucket Server and Data Center now supports IPv6
If you upgrade to Bitbucket Server 5.8 you will see that IPv6 is now supported. One thing to be careful of, is when using Bitbucket Server in IPv6 environments, we recommend that hostnames rather than IP addresses are used.
For example, if you're accessing Bitbucket Server using an address like
2001:DB8::1. instead use a hostname such as
Refining the process of creating a Jira issue from a pull request
Previously in Bitbucket Server 5.3 we shipped a feature allowing you to link your Jira issues to comments in a pull request.
In the first iteration of this feature, important issue details such as description, type, and status could only be accessed by opening the issue dialog. In Bitbucket Server 5.8, this information is surfaced by default - no extra clicking required!
Improved merging with branch dependencies
If you've ever been frustrated about not being able to delete your branch when merging your pull request because there were other pull requests targeting it, we have some excellent news for you.
We've updated Bitbucket Server to retarget the other pull requests to the branch that you're merging into, before deleting the branch, ensuring the deletion of the branch after merge.
Previously, if there were dependent pull requests, the checkbox at the bottom of the dialog was disabled.
You will now see an enabled checkbox with a link to the affected pull requests that will be retargeted.
Updates to Bitbucket Server developer documentation
You may have noticed we've given a bit of a facelift to our developer documentation in recent times.
Our developer docs have been restructured and refined, with a flatter information architecture and a clearer structure to improve usability. If you want to check out some restructured pages, have a look at the Beginner guide to Bitbucket Server plugin development, or our Experienced guide to Bitbucket Server plugin development.
As you can see, to help with readability, we've split this information into beginner and expert pages, to help streamline the process.
This section will contain information about the Bitbucket Server 5.8 minor releases as they become available. These releases will be free to all customers with active Bitbucket Server software maintenance.
If you are upgrading from an earlier version of Bitbucket Server, check the Bitbucket Server upgrade guide.
The issues listed below are the highlights of all those that have been resolved for the Bitbucket Server 5.8.x releases, and are ordered by votes received.