✓ Pull requests get a makeover
✓ Task improvements in a pull request
✓ Your code is in good hands
✓ More auditing capabilities for admins
✓ Single sign-on with OpenID Connect
✓ A new webhook for source branch updates in a pull request
Pull requests get a makeover
SERVER DATA CENTER
The pull request page has been redesigned and packed full of improvements to make your code review experience smoother, more enjoyable, and less of a tedious Task.
Faster navigation in pull requests
With twice-as-fast content loading while switching between diffs, improved file navigation performance, and smooth scrolling in a side-by-side diff, you just might find yourself having fun speeding through your code Reviews.
A more intuitive design
The workflow for requesting requests has been improved, which will give you a more effective and efficient user experience.
Better collaboration in the diff view
- Comment anywhere in the diff, including on expanded lines of code that weren’t changed as a part of the pull request.
- Comment on files stored via Git LFS.
- Syntax highlighting: Until now, syntax highlighting was only available on the side-by-side diff, but now it’s available in the unified diff too.
- Word wrap: No more horizontal scrolling to read lines of code in the diff.
- Expanding: Click Show more to expand all lines in the diff now, rather than just 10 at a time.
- Searching: You can now use your browser’s native Ctrl+F action to search for code in the file you’re viewing.
- Image thumbnails: Drag or attach an image into a comment and you’ll see a thumbnail-sized preview of it rather than having the full-sized image rendered.
Do more with less clicking
- Copying: You can now copy code from just one side of the side-by-side diff view without also copying code from the other one. Also, select and copy branch names in one click.
- Pasting: When you paste code from a pull request into a comment, we’ll automatically format it as a
code blockwith the correct syntax highlighting.
- Editor: When you type into a comment or description editor in a PR, you’ll see Markdown hints as you type, no need to preview until you’re ready to see the final view.
- Filtering: Easily locate changed files in a pull request using the new Filter file tree button. Use wildcards to find what you need faster on pull requests that have a great deal of files to look through. You can find it just above the file-tree, along with the Search code button. To see an example, check out Review and discuss a pull request.
Redesigned icons: Icons in the file tree view now have a more distinctive design with contrasting colors so that you can better recognize the relationship between them, and whether your file has been edited, added, removed, or modified.
Task improvements in a pull request
Create tasks in your pull requests without having to write a comment first. In fact, you can even convert comments into tasks. They also now support Markdown and rich content, like code snippets. Check the Review and discuss a pull request page for more details.
Your code is in good hands
SERVER DATA CENTER
Code Insights for Bitbucket Server provides your team with an excellent way to improve code quality by allowing continuous integration (CI) and other analysis tools to gain insight into code quality for pull requests. This allows code quality related issues to be viewed and addressed during a normal code review process. Now you can access your code coverage results as part of Code Insights.
Code Coverage finds aspects of code that may not have been adequately covered by testing. The results are compiled and displayed in Diff view using color-coded blocks representing lines of code that are fully, partially, or not covered by tests. You can also view a coverage report if this is provided to see the lines that are actually not covered and thus identify critical parts of your application that still need to be tested.
More auditing capabilities for admins
SERVER DATA CENTER
Atlassian has made some improvements to project and repository auditing and extended it to the global management settings that display all events in the system. This digital record gives administrators the higher level of visibility they need to ensure security and compliance.
Let’s talk about what you can do with auditing without having to leave Bitbucket:
→ You get one source of truth. Your audit log is now instance-wide and not limited to a project or a repository, so you can view all the events in one place.
→ You are now in control. You can decide which events are logged and how long you want to keep them. They are also ready to be exported if needed.
→ You get full transparency. You can search the logs using full-text-search capabilities, filter the events, and expand each event for further Details.
Single sign-on with OpenID Connect
Many organizations still have difficulty using industry standard user management tools to authenticate their users in Atlassian tools. A few months ago, Atlassian added SAML support for all its data center products, and now offers a new authentication option with the introduction of an OpenID Connect integration. This allows seamless integration with many third-party identity solutions.
The plugin is available in Atlassian Marketplace for the the following Data Center products:
A new webhook for source branch updates in a pull request
For example, when the source branch of a pull request is updated, new changes after incorporating code review feedback are moved to that branch and the Webhook is triggered.
Enforcement of supported operating systems
Bitbucket Server can no longer run on unsupported operating systems This is due to some memory consumption improvements. The change from using Java ProcessBuilder to manage git processes to a different approach based on native operating system APIs made this necessary.
However, this does not change what platforms are supported, but simply forces the supported platforms that have always been there.
In version 6.9 of Bitbucket Server, a check was introduced to determine whether or not you are working on a supported platform. If the system detects that you are not on such a platform, it will show you a warning banner and a warning in the user interface. If you are on an unsupported operating system, a system error warning will be displayed in 7.0.
A modified behavior for diffs
Pull requests were changed from a 3-way diff to a 2-way diff. This means that starting with Bitbucket Server 7.0 and later, when a pull request is displayed, the displayed difference is between the tip of the source branch and its common predecessor with the target branch. The user interface still shows when a pull request displays conflicts, but these conflicts are no longer marked in the diff. Using a 2-way diff is an industry standard and reduces CPU load on large instances.
The Bitbucket Server client web fragment APIs are replaced by the Atlassian client plugin on the pull request page. If you are creating your own integration or plugin, go to the API Changelog to see how this may affect you.