Ulrich Kuhnhardt [IzymesDev] Rising Star

Workzone monitors the calls to the REST Resources Provided by the Atlassian Stash Build Integration Plugin. As far as I know Bamboo 5.7 is POSTing build results to all connected Stash servers.

I18nBean i18nBean = new I18nBean(jiraAuthenticationContext.getI18nHelper()); with Constructor dependency injection for your report component public class StackedReport extends AbstractReport { private final JiraAuthenticationContext jiraAuthenticationContext; public StackedReport(JiraAuthenticationContext…

I wouldn't expect any problems as the Java 8 VM can execute any bytecode compiled to Java 8 or lower 

Check Workzone for Stash add-on which lets you configure groups for Pull Requests 

Hi Lilach, you may choose to use a Bitbucket (Server) Add-on that does that for you. I know of 2 add-ons that can add normal and mandatory reviewer groups * PR Harmony (Free) : https://marketplace.atlassian.com/plugins/com.monitorjbl.plugins.pr-harmony/server/overview (not sure it does mandatory groups though) * Workzone…

For >2000 user tiers please contact sales at Atlassian dot com directly. They will provide you with a quote. 

The POST request header must contain Content-type = application/json 

My 'watch' setting from old a.a.c don't seem to be active here, though. Can you confirm?

settings from old answers haven't been migrated?

If I understand correctly you need to authenticate Bamboo to Stash as a real user. You can set up the application link between Bamboo and Stash based on Basic Auth (username+password). See also https://confluence.atlassian.com/display/BAMBOO/Configuring+Stash+build+status+notifications

Hi - reviewer configurations are only possible on branch level. An additional option is to add 'suggested' reviewers based on the commit history. If that's not sufficient for your use case please create a feature request at https://bitbucket.org/izymesdev/workzone

Make sure users have the right view permissions for the repository 

We usually use Active Objects to store data in plugins. It is also possible to store simple key-value data in the plugin settings service > example. Your best bet is to write a small add-on that provides the REST endpoints, data storage and web-fragments.Best, Ulrich [Izymes]

you could use the Workzone REST API to get settings for each project/repo

I'm confused about the wording. Are release/* , develop/* , feature/* repositories (and not branches)?

Eric, the Bitbucket Notifyr can do this for you - https://marketplace.atlassian.com/plugins/nl.stefankohler.stash.stash-notification-plugin/server/overview The Atlassian Marketplace has a plethora of great core product enhancements - always a good place to start the search for a solution. Hope it helps - Cheers Ulrich 

Suggestion (plug) With Workzone you can set mandatory reviewers on branch level. The PR cannot be merged until all configured mandatory reviewers have approved.

Use Java8 only. 

Workzone uses the public Bitbucket API when auto-merging Pull Requests. This is technically the same as if you click the merge button in the UI. Changes will be propagated by BB server internally. Workzone does NOT perform SCM level write operations directly to repositories at any time. That's all done by the code…

Hi Tim, Sorry about the trouble. We've had an issue previously with incoming build results in rapid succession which confuse the auto-merge process. Please have a look through this ticket and see if that matches your problem. Basically an incoming build result can trigger an auto-merge (if criteria are satisfied) - another…