G2

Sree K.

Software Development Engineer in Test III

Computer Software

Mid-Market (51-1000 emp.)

8/1/2026

"Reliable Version Control with Smooth Branching, PR Reviews, and Jira Integration"

4.5/5

What do you like best about Bitbucket?

I’ve mainly used Bitbucket to manage our automation framework and collaborate with the team on code changes. It’s been a reliable place to keep everything properly version-controlled, whether that’s Playwright scripts, API automation, or broader framework updates.

What I especially like is how straightforward it is to create branches, open pull requests, and review changes before anything gets merged. That workflow helps keep the codebase organized and reduces the risk of people accidentally overwriting each other’s work. Since it integrates well with Jira, it’s also easy to link code changes back to user stories or bug tickets, which makes tracking and follow-up much simpler.

For day-to-day development and automation work, it does exactly what I need and doesn’t get in the way. Review collected by and hosted on G2.com.

What do you dislike about Bitbucket?

I don’t have any major complaints, but certain parts of the interface can require a few extra clicks compared to other Git platforms. For example, when I’m browsing commit history or comparing larger pull requests, the workflow can sometimes feel a bit less intuitive than I’d expect.

Merge conflicts are really a Git issue rather than something specific to Bitbucket, but dealing with them can still be time-consuming when several people are working in the same files at once. Aside from that, Bitbucket has been stable and reliable for my everyday work. Review collected by and hosted on G2.com.

What problems is Bitbucket solving and how is that benefiting you?

It helps the team manage source code in a more structured and reliable way. Rather than sharing framework changes through files or email, everyone can work on their own branch, open a pull request, and have the updates reviewed before they’re merged.

For automation testing, this is especially helpful because multiple team members can work on different test scripts at the same time without impacting the main branch. The version history also makes it straightforward to see who changed what and to roll back changes when needed.

Overall, the biggest benefit is keeping code changes organized and making collaboration across the team much smoother. Review collected by and hosted on G2.com.