1. Home
  2. Version Control Software
  3. Bitbucket Reviews
  4. User Review of Bitbucket
Cost Effective and Intuitive Tool
August 01, 2017

Cost Effective and Intuitive Tool

Anonymous | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with Bitbucket

Bitbucket is currently being used as our primary source control tool across development and data teams. We host all of our code, data operations scripts, SSIS projects, etc., in Bitbucket repositories. It's essential for proper code maintenance, collaborating among teams, versioning, etc., as well as integrating well with the other Atlassian products we work with.
  • Easy integration with SourceTree.
  • Perfect avenue for code reviews.
  • Easy to understand interface.
  • More efficient and easy to understand methods for addressing merge conflicts.
  • Assigning access levels and group access is a bit confusing.
  • Better community forums for addressing shared problems with the tool.
  • Drastically cut down on the time involved with project collaboration among cross-department teams. Time is money.
  • Integrated well with tools we were already using, making setup and implementation cost effective.
  • Easy to implement code reviews have saved time addressing bugs and other issues that would arise previously.
The primary reasons we went with Bitbucket over TFS and/or other options are as follows: 1) Ability to integrate with other documentation and development tools we were using. 2) Cost - with our size and current business needs, we were able to implement what we needed in Bitbucket and maintain our codebase in a much more cons-effective manner than TFS.
Bitbucket is perfectly suited for any organizations utilizing Atlassian tools (as our organization does). It takes a tool that works especially well for versioning and team collaboration and elevates it with the ability to integrate with specific projects in JIRA, documentation in Confluence, and general communication across the organization. It also provides good backups for repositories. Some less than ideal scenarios are if you are working external tools that don't integrate directly with Bitbucket.