BluBees Beta v4.2.0: Bitbucket Support, Smarter Flows, and a More Secure Platform

Beta is where we ship and learn. v4.2.0 is our October update — a focused release that expands who can use BluBees, reduces friction for teams building complex workflows, and makes the platform more secure. Three things, done properly.

Here's what shipped.

Bitbucket Support: The Version Control Gap is Closed

Until now, BluBees' source control integrations were GitLab-only. That was a real limitation for a meaningful portion of the development teams we talk to, teams that are fully standardised on Bitbucket and had no equivalent path to the same automated workflows.

That changes with v4.2.0. Bitbucket is now a fully supported connector in BluBees, with the same depth of integration that GitLab users have had access to from the start.

What that means in practice: if your team uses Bitbucket, you can now build Flows that trigger on repository events, create branches automatically, perform file operations, and fire pipeline runs — all orchestrated from within Jira, exactly as you'd expect.

Bitbucket support isn't a minor addition. For teams standardised on Bitbucket, it's the feature that makes BluBees relevant to them for the first time.

The use case that becomes possible immediately: a customer case opens in Salesforce → BluBees creates a Jira Epic → a Bitbucket branch is created automatically → a pipeline runs → results feed back into Jira. The same end-to-end orchestration that GitLab users have been building, now available to Bitbucket teams.

Auto-Inherit Node Configuration: One of Those Fixes That Just Feels Right

This one is harder to describe in a headline but easier to appreciate if you've felt the pain it removes.

In complex multi-node flows, where a node acts as both a recipient of data and a source for the next step, you previously had to manually re-enter configuration details at every node: authentication, endpoints, metadata scopes. In a flow with several chained nodes, that added up to meaningful setup time and a reliable source of configuration errors.

Auto-Inherit changes that. When a node is both a target and a source, its configuration now automatically carries forward to the next node in the chain. You configure it once. The flow inherits it.

This applies to Call-Event and On-Response nodes, consistently across both the execution engine and the canvas UI. Fewer steps, fewer errors, faster flow builds.

Security Update: Backend Dependencies Patched

We identified and resolved multiple security vulnerabilities across BluBees' backend services in this release, covering the API, Tenant Management Console, Scheduler, and Automation modules. The affected third-party libraries have been upgraded to their patched versions across every impacted module.

No customer action is required. We're mentioning it because transparency about security updates is the right approach, and because for enterprise and government teams, knowing that the platform is being actively maintained at the infrastructure level matters.

What's Coming Next

We're actively building the enterprise stack auto-discovery feature, the capability that will automatically map your toolstack and surface recommended Flow configurations across your business tools simultaneously. This is the feature that takes "I want to automate this" and makes the starting point significantly less blank. More details as we get closer to General Availability.

We continue to ship regularly through Beta. If you'd like to be part of the Beta cohort, reach out, and if you're already with us, everything in this release is live now.

Found a bug or have a suggestion? Our support portal is open: blubees.atlassian.net/servicedesk/customer/portal/1

Interested in joining the BluBees Beta? Visit blubees.ai or install the app from the Atlassian Marketplace to get started.