Kristy Atlassian Team

@Casey Wise, maybe I'm misunderstanding your comment but it seems to me that this will result in all the changes from master being on the release branch. If you then want to make a bugfix to that release branch, you may not get what you expect because it will contain all the changes from master too - which may be API…

Hi @David Karr, Does the Stash Notify plugin not place a build status on the pull request, similar to this: "1 build failed" Clicking on this link should open up a dialog: And this dialog contains the links to builds that were recorded. Let me know if I'm misunderstanding your situation, Kristy

What version of Bitbucket Server are you using? Project level administration for default reviewers was introduced in Bitbucket Server 5.2. You see the version you are using by looking in the footer.

Hi @Rinkal Garg, To access the API you need to write a Bitbucket Plugin (see https://developer.atlassian.com/server/bitbucket/how-tos/beginner-guide-to-bitbucket-server-plugin-development/ for details). You can depend on the jar by adding the dependency in your pom.xml <dependency>…

Ah, I see. Tortoise Git cannot use the git executable you have on the linux drive. The Tortoise Git client is a Windows program, and as such you need to install the git client locally on your Windows computers; it is a requirement of the program. Hope that helps, Kristy

Hi @Mark, May I ask why you have this set up? Is there something stopping you from installing git on your local windows machines and cloning directly from Bitbucket rather than have a public share folder? The easiest set up would be just to have Bitbucket running on linux, install git on your local machines, then clone…

The application types are listed here: https://docs.atlassian.com/applinks-api/3.2/com/atlassian/applinks/api/ApplicationType.html All Known Subinterfaces: BambooApplicationType, ConfluenceApplicationType, FishEyeCrucibleApplicationType, JiraApplicationType, RefAppApplicationType

Have you tried: applink_service.getApplicationLinks(BambooApplicationType.class) or applink_service.getPrimaryApplicationLink(BambooApplicationType.class)

Also, in the example you used you will find that the pull request will have a merge conflict because both the source and the target branch modified the same line of the same file.

Hi @Jens Müller, On the 'Create Pull Request' page and the 'Compare Branch' page Bitbucket Server shows a 'common ancestor' diff (also known as a 2-way diff). This diff finds the commit that is common to both the source and target branches (known as the common ancestor commit) and compares the latest commit on the source…

Hi @Mugurel, Apologies if you were notified of my previous (incorrect) responses - I misread your question. I think that the problem here is that you want to restrict 'all changes' for the master branch. This setting can be used in a number of different ways. In your case, you'd like the creation of that branch to be…

You can use the BuildStatus API to get build status' and build summaries for commits that have already been sent to Bitbucket. But, if that doesn't have the data you need, then you can use the ApplicationLinkService to get the Bamboo link and from there you can use the ApplicationLink to get the details you need (e.g.…

Hi @Mark, It doesn't matter what operating system Bitbucket Server is run on. How you set it up depends on whether you already have code on Bitbucket, or whether your code is local and you want to put it onto Bitbucket. If your code is already on Bitbucket, then you simply click the 'clone' button in the sidebar (the first…

No, there's no way to get 'notified' when a PR is ready to merge, but there is a recent suggestion (https://jira.atlassian.com/browse/BSERV-10664) for it. Currently, the only way to find out is by using the GET endpoint you mentioned.

Hi @Matthew Ryan, You are correct that there is no place in the UI to show comments created on a commit without being anchored to a file. This is by design, and it was a mistake that the REST API supports creating these comments. You might notice that the REST API doesn't actually support getting these comments back either…

Hi @Ron Bob, The documentation for branch permissions can be found here and if you find the section that says "Example request representations" you will find an example json request to create a branch permission. The example givein in the documentation is: { "type": "read-only", "matcher": { "id": "refs/tags/**",…

Hi @Arturo, This isn't an answer, but I can't comment on the question itself. Can you please provide some more information to help me diagnose the problem? What version of Bitbucket Server are you using? Is it possible you are experiencing this issue which was fixed in 5.9? Also, to try and narrow down the problem, does…

Unfortunately it is not possible to search for code in this way. Cscope is able to do this because it is aware of the language's syntax, where as Bitbucket's search is required to work for all languages and doesn't have any language-specific functionality. Bitbucket does try and be smart with how it shows its results,…

You have two options to resolve the conflict: 1) Resolve them without a pull request. To do this, you would checkout the master branch, and then pull in the release branch. This is effectively the solution that Bitbucket Server give you when you ask for more information on how to solve the conflict. $ git checkout master$…

When you push onto release/2 you are have effectively merged master into release/2. This is not what you want to do if you would like your release branch to not contain all the commits that exist on master.

Just letting you know that BSERV-2924 was closed in 4.8 release, so now you can add default reviewers on your pull requests

There is a JIRA ticket open for this suggestions. You should watch it so that you can receive future updates on it. https://jira.atlassian.com/browse/BSERV-2924

Hi @Kevin Thomas, As of Bitbucket Server 4.9, we provide a repository import feature. You could use this to copy one repository into another project.…

Bob should only commit his changes and not push them until he is ready for the pull request to be reviewed again. This way, the pull request remains in the "needs work" state until the previous feedback has been addressed. Alternatively, if the changes need to be pushed to the sever (for example, if he is working on…

I have edited my answer to include details about the API. Hope that helps

Through the UI: On the commit url (https://bitbucket-server-url/projects/project-name/repos/repo-name/commits/commit-hash) at the top right of the page, there is a section that will show the related issues, next to a JIRA icon. Edit: Sorry I didn't realise you were looking for an API. The REST APIs available for…

Hi Sobiero, Bitbucket Server does not come with an issue tracker as is expected that users integrate with JIRA. If you are having trouble integrating your Bitbucket Server instance with JIRA I recommend that you open a support ticket. Hope this helps, Kristy

Atlassian has a very helpful tutorial that explains what pull requests are, what they are used for, and how to do one. https://www.atlassian.com/git/tutorials/making-a-pull-request 

It sounds like what you want is the Bitbucket Server Archive Plugin by Atlassian Labs. Unfortunately, it does not archive all branches and tags though. For more information on its capabilities, see https://bitbucket.org/atlassian/stash-archive/overview. Hope you find it useful, Kristy

In the search bar at the top right, type the text you want to search for. If you don't click 'enter', Bitbucket will search for repositories that match your terms and put them in the dropdown that appears under the search bar.