Bitbucket Reviews & Product Details

Easy to use. Important features are not hidden behind layers. Easy to add a reviewer, clone a repo, and look at commits.

It can be confusing trying to delete a branch

Source control. It's a great tool and more intuitive than GitHub in my opinion

1. Simple UI which is very easy to work on 2. Inbuilt integration with Jira makes my work very easy to do 3. For Each and every commit we can easily track the changed lines from the code 4. Best feature is we have separate tabs for multiple options such as branches, commits, and pull requests. In this way, it is very helpful for better productivity.

1. Should have an option to access public repositories. Most of the public repositories that I'm finding is not from the bitbucket. All are from its competitors 2. Other than that nothing I found as negative.

1. My Team can work individually and independently. 2. Can approve or reject based on code reviews. 3. If any problem came with the current version of the software we can easily track the code and identify the problem to fix the issue 4. we can also revert to the previous version by just single command

Bitbucket is perfect for hosting git repositories and organizing teams around projects. The application allows you to host wikis, working groups, and actual source code. The application is easy to navigate and enables you to host projects privately.

The community of users is not as large as competitor GitHub

Source Control and Hosting, Team Management and collaborative programming

Bitbucket was a great platform to use Git. I like it most because it provides an environment that enables team members to work together on a project, and it gives features like code reviews before pushing it to the repo. Also, We can integrate Bitbucket with Jira, so it helps a ton for agile development.

I have not faced issues during my usage, so nothing to say on this section. I have learned many things during muy usage of bitbucket and no negetive experience.

We have been using bitbucket with teams, and it saved a lot of time. And it was effortless to find the bugs while reviewing PRs, and I learned best code practices and techniques from my seniors.

I like it's simple interface and it's blue white theme rather than High contrast colors like github. Even a beginner can understand things effectively in bitbucket. Although it serves same purpose as github, I personally choose bitbucket.

Not found anything yet. But interested if it adds a feature that can roll back specific commits.

I am using bitbucket for version controlling of my company's project code base. Added tags new branches and classified various versions of same code

Versioned code and documents Verty well structured git based tool

UI could have been better Commands are little bit confusing compared to git

Software code hosting and collaboration with versions Helpful for whole team

Effective UI/UX and easy-to-use functional implementation are the best things about Bitbucket. Having too many options for active usage ends up cluttering the screen, but the minimalistic screen makes it clean and easy to use with a sidebar to help out easy navigation between a set of linked tools.

I couldn't find any issues when compared with similar tools I've used earlier.

My primary use of Bitbucket is for managing code repositories along with keeping track of tasks assigned on Jira. The best thing with code repo is that it has a sleek design to show categorized features on the left, making it easier to access any option on the go.

Like everything Atlassian, it's straightforward to use and figure out how to utilize best. If you have any familiarity with git, you'll figure this out very quickly.

It's not the most customizable in some areas

Pipelines are very easy to create to get CI up and running. I also really like the code review process in the application - it's very easy to read the code mods and comment/address them.

I am using bitbucket for the last year, and it looks like my experience is changed. Bitbucket is a place where you can manage your data or code under multiple branches, and then you can club it to the main branch. The best part is that it is on the cloud, and everything is soo transparent. You can put create merge requests manage feature branches at your ease. At the time of merging of new code to the repo, an approval system is the which will ask the approvers to approve the code, and once approval is done then you can commit the code. The user interfaces are tremendous and super handy to use. It has excellent connectivity with Jira and visual studio code. We can directly put code to bitbucket using SFDX and using git commands. This tool offers a complete package for storing data whenever and wherever it is required.

There is nothing which I can say I dislike about bitbucket. Maximum is they can improve their user interface to make it look more attractive to the users and with different themes.

When we have multiple people working under the same project, then we have to take care that code that is deployed to bitbucket should be updated and posted on top of the code submitted by others. There is a process to create pull requests to a branch, and on top of that, we can add our changes with approval from the lead of the project. This makes the process very transparent and very simple to use.

Many things! Easy to use. Compatible with git version control. It can be integrated with Jira conveniently. Once the code the merged, you can submit pull requests, and teammates will review and can comment on them. Very useful and convenient to test the code. It uses public and private key encryption for security which is fantastic! GUI is user-friendly!

Slow as compare to GitHub and pipelines take time to run too long, and that's nothing compared to its pros! The premium plan is expensive than Github.

I use bitbucket every day to merge by code. I have multiple repositories, and all are very convenient to use. The best thing is it uses encryption keys to keep your code safe.

Quick and easy. There are a lot of integrations to 3rd party services that help with the development process. Makes setting up new code projects and repos fast for the development team.

The user management console is a little confusing. The user management seems like it could be simplified to make it more streamlined and less confusing for when adding/removing users and groups.

We need a Cloud-hosted code repository for our development team makes our development effort easier. Not having to host and maintain a service like this allows our infrastructure team focus on core business needs.

Easy to start with. Later once we scale, I think it's easy to scale our business.

The prices should be users in groups, like for first five users some price and rest different price

team meetings in different remote places

I use the GitHub function to compare a dataset master to an updated file. This gets me a list of all the changes between the two files, so I can just post the changes. Then the system allows me to update the master file with the changes. I then repeat the process every week from March to October. We have 2300-2400 eContracts memberships for 0ver 66 different contract types with over 200 different school entities to keep track of. Bitbucket coding using GitHub saves 90% of the time involved (reduces several hours to several days time determining the changes to only 30 -120 minutes posting the changes only). A massive amount of time saved, as the system is not able to be automated.

I do not have a problem with this software.

Managing contract memberships and discounts for fee-based course offerings.

- Simplistic and easy to use Interface - Inbuilt Web Editor for small changes on the go - Excellent integration with Jira for easy issue tracking - CI/CD pipeline already provided, for seamless development/deployment process - Track and view past history of PR's and Branches - Hierarchy for managing different products of organisation - Direct issue issue status update with commit special commit messages directly reflected in Jira

- Sometimes the description is not auto updated when creating a new Pull request to a different branch

- Auto deployments using pipelines - Codebase management - East tracking of Pull Requests and feedback for the same

The best part about bitbucket we can control version and share our repository with anyone with in the organisation.which helps in faster development without any conflicts.

As of now I haven't found any dislike about it.

Taking updated code,creating own branch ,made changes and raising pull request from cmd/git gui/ or from eclipse.which help me in development of project.

the easiest way to control git tree and project and the connections with Jira and other tools

The user relation with email to control access

Control my project

I am using bitbucket since 2015, at that time github was paid for private repositories. So I made my account on bitbucket for private repositories and I was amazed to see how good and easy to use their user interface was. Bitbucket's integration with jira is the most loving feature, so you can keep track of the errors and tasks. I also used confluence for documentation, it is also good to integrate with bitbucket. It's GUI based desktop app solves the problem for those who don't know how to use git console based commands.

To be honest the services provided by the bitbucket are very good and easy to use, so you can't hate them. I personally like all the features.

Code version controlling was never an easy task before git, so main problem I am solving version controlling problem with bitbucket. Second it's integration with jira helps me to keep track of errors and tasks.

I like that bitbucket is free, it has pleasant UI. Bitbucket has free private records for little groups or possess utilization. It is an extraordinary preferred position contrasting with GitHub. They have possessed a program for overseeing variant control of your venture locally, it is called SourceTree. It is pleasant particularly for new engineers who are inexperienced with git to utilize it from comfort.

There is a cutoff to a number of clients getting to the record. This instrument has much personal time. A new element has a touch of expectation to absorb information wherein demo would do the trick the need about another element.

Bitbucket has made it excessively easy to add form control practices to our association. On account of the joining with Slack, the entirety of the engineers can without much of a stretch see and audit each other's code from directly inside the suitable channel. The maker of Bitbucket, Atlassian, additionally made SourceTree which is a free form control apparatus that makes it so you don't need to depend on the order line. It works truly well and has helped profitability.

BitBucket is a great version control tool and a platform to keep our project update when developed by a number of people. It helps us to keep track of all the modifications and updation done by each and every user in our repository . It helps us to share our latest bug-fixing with our peers instantly. Not only it helps us to share our code but is also helps us to manage our main repository in such a way by keeping reviewers who receive the request to merge the new changes in our code. This prevents unnecessary and multiple updating in our main repository

There is nothing to dislike about bitbucket.

By the use of bitbucket, we can share our code easily with our colleagues in our organization and see the updation or correction done by each and every individual.

Pull requests allow specialists to test & accept code before it is accessible to each other and helps keep reliability code that contributes to quality software. More annoying quirks such as Pipeline allow the user to much more regularly deploy / release.

It also has proven to be effective in line with certain goals so far. Maybe we could assume that perhaps the costs increase very quickly for very huge teams and that in some situations this could be perceived as detrimental.

It's really a great way to make entirely convinced developers focus on what they are doing, n't seem sniffing around rather than getting stuck in many dozen certain repositories that don't affect their job.