Anton Genkin Atlassian Team

Thanks everyone, we are finishing this round of research. We'll let you know on the next opportunity to share your thoughts and experience in the future.

Hi everyone. I'm Bitbucket DC Product Manager and I'm happy that we now have this group. I'll make sure you guys are updated on all important changes. Lastly, if you have any questions about Bitbucket DC or Atlassian dev tools, I'd be glad to answer those.

Hi Community, we still have a few seats available for interviews. If you'd be interested in sharing your company's plans regarding staying with Bitbucket Server / Data Center or migration to Cloud, please register. Or if you have a customer who is considering migration to Cloud or decided not to, we would like to discuss…

@Brian Duguid thanks for spotting the issue. The form is fixed now and ready to ready for submissions :) 

Thanks for all the insightful discussions we had with all of you in the last month. It helped a lot to better understand your current needs and plans for the future. We have finished this round of interviews, so we won't accept new volunteers for a while. Keep an eye on our posts in the Community, we'll publish a new call…

@Daniel Juravski there is no global setting that changes the default state of this checkbox. The state of the checkbox is saved per user/repository. For example, if you choose to delete branch after merge in repository ABC, on next merge the checkbox will be checked. If you still need to have this checkbox checked by…

If I understand you right you'd like to get the list of PRs of all the users from your team from a specific repository, without sending requests for each specific user (PR author). According to REST API docs you can use the following end-point to get the list of pull-requests from the repository, then filter that by the…

@Suporte STI More on 3-way diff - https://community.atlassian.com/t5/Bitbucket-questions/How-to-enable-3-way-diff-in-BitBucket-7-0/qaq-p/1331371#U1332687

@Geoff Goodhew the documentation above is for Jira Software Server, not Jira Cloud. The list of supported statuses of pull requests is bigger in Jira Server. Here is the doc for Jira Cloud - https://confluence.atlassian.com/jirasoftwarecloud/advanced-searching-developer-reference-967312910.html

For Jira Software Server you can find the full list of available development fields here - https://confluence.atlassian.com/jirasoftwareserver/advanced-searching-fields-reference-939938743.html

@alexmears If you use Jira Software 7.8+ integrated with Bitbucket, then the following syntax will work: * Issues with PRs (any PR status): development[pullrequests].all > 0 * Issues with open PRs: development[pullrequests].open > 0 * Orphaned changes: development[pullrequests].all = 0 AND development[commits].all > 0 *…

For Jira Software Server you can find the full list of available development fields here - https://confluence.atlassian.com/jirasoftwareserver/advanced-searching-fields-reference-939938743.html

Hi, I'm product manager at Atlassian running research on preferable Data Center deployment options. I would highly appreciate if you could answer questions from a short survey on the topic. Your answers will help us a lot in prioritisation of new Data Center deployment options. Survey →…