Bitbucket Server 4.2 release notes
8 December 2015
If you are upgrading from an earlier version, check the Bitbucket Server upgrade guide. Also, be sure to see the End of support announcements and the changes listed in the API changelog.
The Bitbucket 4.2 changelog is at the bottom of this page.
Smart Commits
Smart Commits allow repository committers to process JIRA Software issues using special commands in your commit messages. Bitbucket Server 4.2+ comes bundled with support for transitioning, commenting, and logging work to JIRA issues using commands entered directly into commit messages.
Smart Commits from Bitbucket Server work with JIRA Software 7.1+. For more details on using Smart Commits, see Use Smart Commits.
Application links diagnostics
Bitbucket Server now bundles a completely overhauled Application Links experience that comes with built-in diagnostics and link status lozenges.
Now you can see what’s going on with your integrations and easily get the troubleshooting information you need to resolve any broken links.
For now, you'll see the new diagnostics if you're a system admin and you only connect to Atlassian server (not Cloud) applications using OAuth authentication. Read more about the new application links.
Small improvements and bug fixes
We've made the following small improvements and bug fixes:
- Comment forms that hit the nesting limit are no longer misaligned.
- Plain Delegated LDAP configuration no longer mistakenly uses hidden forms.
- Updated Apache Commons Collections to v3.2.2
- HipChat plugin connection no longer fails with SQL Server database
- Allow specifying the multicast IP for Hazelcast in Bitbucket Data Center
Change log
This section will contain information about the Bitbucket Server 4.2 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 Stash, check the Bitbucket Server upgrade guide.
The issues listed below are the highlights of all those that have been resolved for the Bitbucket Server 4.2.x releases, and are ordered by votes received.