Ulrich Kuhnhardt [IzymesDev] Rising Star

I asked Rovo IF she could create work items for me based on an epic. She said "yes, would you like me to go ahead and create them for you?" - very sweet! I said, "yes please" Rovo then found out that she couldn't create issues :( I thought it'd be something with my set-up, and contacted ATL support. They confirmed that…

Woohoo Benediktiner Helles!!! Hans knows his beers!

Fantastic idea! Thanks for sharing. 

Bit late to the party, but here is good news. We have released pull request merge hierarchies in Pull Request Organizr via an intuitive drag and drop method to create multi-level pull request merge dependencies. Linking and unlinking pull request dependencies Check out the blog ...

That's covered. Let me know how it goes.

The AI back-end also runs natural language processing for french language. Which languages are you after?

Try this 'Post functions' solution.

I tried this solution on both JIRA server and cloud. No need for script runner.

Can you please create a Workzone support ticket and attach the relevant bitbucket log that contains the stack trace. We'll look into it.

What does the json payload (string) exactly look like? 'Wzautomerge' won't be matched by the server as a data element.

Try workzone for Bitbucket. It allows you to configure advanced merge restrictions on branch(pattern) level. Available for Bitbucket 4 and 5. 

Workzone for Bitbucket now supports file and directory based reviewers.

You can control the merge-ability by adding required reviewers for a repository - then add a merge check to your repository configuration. If you want more fine-grained control over who reviews pull requests and when and how a pull request is merged you may try out the Workzone for Bitbucket add-on.

There is also the workzone add-on which lets you add default reviewers and groups by branch or branch-pattern via an intuitive UI. Mandatory reviewers are also supported. The repository reviewer configuration can be used to control the pull request merge process as well - if that's part of your workflow. Let me know if you…

@b bopanna would you please elaborate why branch permissions won't work for you? 

You would need create a plugin that will do that for your or use an existing plugin. There are a few available on the Atlassian MP listing for Bitbucket Server. I know of 2 plugins * Script Runner : https://marketplace.atlassian.com/plugins/com.onresolve.stash.groovy.groovyrunner/server/overview *…

You would want to write a little pre-receive hook that checks * if branch has outgoing PR(s) * If so - are there any approvals yet * If so - rejected the push to the branch. There are some good hook tutorials in developer.atlassian.com. Hope that helps

Resolved with Workzone version 4.3.2 - leave the auto-merge user field blank.

Hi Bijoy, you are right - currently the auto-merge user must have repository/branch write permissions when the auto-merge configuration is saved - and yes - you can revoke those permissions later. Another work-around is to use branch patterns - auto-merge user permissions are not enforced during configuration when you use…

Hi Bijoy, I understand that you don't want to trigger an auto-merge upon approval. Do I understand correctly that you want to prevent the PR to be merged if the condition is not satisfied and to be merged manually only when the merge condition is satisfied? 

Hi there, The Global Pull Request Organizr is a recent submission we are still working on publishing its REST Api documentation. For now please use the following Labels POST http://host:7990[/bitbucket]/rest/organizr/latest/labels/projKey/repoSlug/pullrequestId Payload JSON{ labels: ['label_a', 'label_b']} For DELETE and…

With Workzone you can define reviewer groups whose members are added to a pull request when it is created for a configured [source]/target branch.

Arun, not completely sure why the new set of crowd users are not recognised. I suppose they have the same usernames and group memberships? The only reason I can think of is that Bitbucket checks permissions against user's uuids which may differ between old and new crowd instance. You can retrieve existing Workzone…

Sorry for the trouble.Could you please elaborate what stopped working? Are users not listed in the workzone reviewers configuration? Are they not added to new Pull Requests?

Users with repository READ permissions can be added as reviewers. Are you requesting to block adding any reviewer to a Pull Request or only selected users? Do these selected users need to see the repository?

Ed, the price for Workzone for Bitbucket (server, datacenter) for a 5000 user license is USD 6000 or USD 4000 for a 2000 user license. Last time we checked there was no 3000 user tier for add-ons. All licenses are sold via the Atlassian Marketplace. We as developers don't sell directly. Please contact sales at atlassian…

https://confluence.atlassian.com/bitbucketserver/automatic-branch-merging-776639993.html

If you adhere to a particular branching model based on git-flow you can enable cascading merges in Stash/Bitbucket server. 

Hi John - I've confirmed the following to work# In Bamboo app links configure *outgoing* Authentication as basic auth like http://cl.ly/image/3F3W2K2m380u# In Bamboo plan configure notifications for Stash like http://cl.ly/image/2j3l450x2238 . Note the hint to configure *Basic Auth* between Bamboo and Stash# In Stash app…

We have encountered some problems with Bamboo 5.7 when an OAuth based application link is configured between Bamboo and Stash. Problem The POST request from Bamboo seems to be authenticated via app-link OAuth challenge and is not associated with a stash user. When Workzone tries to find open pull requests to match the…