You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We recently shipped Bitbucket Server 6.2 at the beginning of April, which contained a number of improvements to help streamline developers' workflow and minimize errors. We wanted to take a second to highlight a few of these improvements and get your feedback on these new additions.
1). Repository descriptions: Many of you have hundreds of repos per project and we’ve heard that it can be challenging to find the exact repo only using the repo name. Gone are the days where you have to spend time going inside each repo to Readme, which is not always there or trying to use alternative ways like Confluence pages. Short descriptions can now be added to repos to provide additional context - allowing you to quickly and easily find what you are looking for. You can add these when creating a repo, or through the repo settings page.
2). See absolute timestamps: Two days ago? What day was that? You’re in luck - you’ll no longer have to ask yourself these types of question. You can now choose to view all timestamps in absolute format (e.g.: 7 Apr 2019 2:00PM), instead of relative format (e.g.: 2 days ago) for increased precision. Head to your account settings to make the switch.
3). View SVG source code: Today, when users are reviewing and working with SVGs, they can’t see the source code, only the image. And worse yet, if your SVG code is improperly formatted, you might even see a broken link. Users need to be able to view this code so they can review it properly. In this release, users can now see and edit their source code directly in Bitbucket. This can be done in both diff and source view.
4). Delete confirmation check: Mistakes happen. We’ve all accidentally deleted a project or repo at some point in time. To prevent these accidental deletions, we’ve added an additional layer of security or check — users first have to enter their name before they can delete.
5). Customize your support link: We all have issues signing in from time to time. With our new customized support link, we’re helping users get back into the product faster. You can now customize the ‘Contact Support' link in your instance footer to direct them to a custom URL (e.g.: that of your support desk) or to send an email (e.g.: to a system admin), rather than the standard Atlassian support contact us page. Want to learn more? Look for footer.links.contact.support on our config properties page.
6). Support for Git 2.21: We strive to support the latest versions of git as soon as they are released. So in Bitbucket Server 6.2, we’ve added support for having Git 2.21 installed on the server.
We’d love to hear your feedback on these improvements and how your teams will take advantage of these new features and improvements. Share your questions and feedback below in the comments and a member of the Bitbucket Server and Data Center team will be ready to respond!