This is it! This is the project you’ve been waiting for. The one that’s going to define your career and challenge you and totally transform “the way things are done around here.” The project your team will point to five years from now as the inflection point that ushered in a new era of awesome. If, that is, you can get the project approved, prioritized, and properly resourced.

The one I’m talking about was a meeting with my boss in one of those conference rooms with clear walls, like a fishbowl, when she told me I didn’t get promoted. I’d had a fun, intense, wild ride working at a late-stage startup. But three years later, I felt like a shell of a person. I was commuting ninety minutes each way to work. I was feeling uninspired, dreading the relentless marketing campaign cycles that at one time were exciting.

We’ve all been on two types of projects: ones that ran smoothly, and ones that crumbled to pieces. While there are lots of contributing factors in each case, I’ll go out on a limb and say that project ownership (or lack thereof) is what makes the biggest difference.

Developers understand the importance of keeping their team up to date on work and use many of the integrations between Bitbucket Cloud and Jira like smart commits and automation triggers to do so automatically. However there may be times where there are nuances or uncommon situations when merging a pull request that aren't covered by existing automation rules – sometimes there are multiple pull requests, or sometimes merging means you're now in 'Done' and other times you're in 'Releasing'.

Bitbucket Pipelines provides teams with a one-stop solution to build, test, deploy and track their code, without ever leaving Bitbucket. Developers and release managers can easily track and visualize deployments, while non-technical teams can have visibility into what features are coming down the pipeline.

While working from home is the new normal, communicating and collaborating virtually hasn't become any easier. And for developers, being productive while at home has its own set of challenges (we're thinking of things like figuring out how to pair program over Zoom or how to make do with only a single monitor). In times like this, our engineering team has been relying on one short-cut towards productivity: the Bitbucket Cloud bot for Slack.

We're happy to announce that on September 15th, 2020, we will begin gradually enabling a new traffic acceleration improvement for all Bitbucket Cloud users (Free, Standard, and Premium) when accessing Bitbucket.org for Web- or Git-based (ssh/https) operations. This new improvement leverages AWS Global Accelerator to route traffic to and from Bitbucket Cloud via 83 Points of Presence in 73 cities across 38 countries, potentially dramatically speeding up transaction times.

Today Bitbucket is releasing a new labs feature, "Pending Merges", which allows for automatic merging of pull requests when builds pass. This means no more continually checking back in on your pull request, just waiting and waiting for your builds to pass before you can finally merge it. You will no longer be forced to begrudgingly fix that one-character whitespace typo in your comment that you really should fix, but that means you're in for another 30-60 minutes of watching your builds.