Bitbucket Room for Improvement

Javad-Talebi
Team Leader at Turk Telekom
While it is a good and useful product for my application, there are several disadvantages to the system. One thing I have seen is that you can't add some better features to the wiki system. For example, better attachment and document management could be more useful. We actually use another system for our documents because the document management system was not suited for us. Maybe they can improve the wiki side of that product. The issue tracking also can be better than it is now. The wiki side of the system can use the most enhancement. When I want to use the wiki, I have many problems writing the source code in different code languages. We are creating a web program. Because it is a web project, we want to use, for example, JavaScript and we use CSS. Then we want to use Java for the back-end. When we use different languages, we have a problem deploying them with that system. Sorting documents is an issue, and also issue tracking over in the system is not very professional. If you compare this product with JIRA it is not very good in these capacities. There is a lot of room for improvement. Another comparison could be made with teamwork.com which is better at these things. We used teamwork for a situation where we needed both better document handling and better issue tracking. We wanted to have something like GitLab with all the features of a project management tool. Another problem that I had involved issues with CICD (Continuous Integration Continuous Deployment). I could not configure it easily. I did not try to resolve the issue and left it for the future. Maybe it was because of the user interface or maybe because the documentation was not so good, but the CICD pipeline wasn't very easy for us to use. Maybe just adding more helpful documentation for that feature will solve the issue. The limit on the number of users became a problem for us because we live in a country in the Middle East. The issue of spending more money and having additional costs is a really big concern for us. For example, for being the Turkish leader in the field, what we were able to charge the customer compared to what we are paying for services is not cheap. That makes it difficult to make a decent profit, re-invest and grow. Other additional features I would like to see can help expand how we work with customers. One example is adding a notebook. There is no notebook in the product at all to write notes for your users and customers to remember details about them and have them available. Another example would be to add a feature that allows you to integrate and converse with GitLab. Sometimes we need to write some notes for something inside GitLab, but it would be good to have the availability to add from both products and have them integrated. If BitBucket had online chat and online help for premium users, it will be best for users who need to get support. Programmers want to focus on the code. For example, if I want to configure something in my pipeline or in a product I am building, I may need to read 30 articles to understand what is happening on the system in order to program it. If I am in a rush and I am a programmer, I don't have enough time for that. So if BitBucket had an online chat system for support to help the developers, that could speed up development and access to support itself. I can understand these things may not be the primary purpose of the BitBucket solution, but maybe if these things can be added the solution would be more independent, better integrated and would be nearly perfect. View full review »
Avinash Behera
Associate Tech Lead with 501-1,000 employees
It has a distinct tree type of structure that any branch that you need to create can only be a replication of, more or less, of the changes. You can not have a branch that is totally different from the root. This is an advantage but also a drawback. Being a developer, I would prefer to have these kinds of rules. But again, that does not allow me to use the same repository for a different kind of structure so I would need to create a new repository if I am changing the whole structure of the application. You can say both, it is a drawback or it is plus of the application. Another thing, the time it takes for the repository to get downloaded and be available increases if you are using the cloud version. The only thing we can improve is the bandwidth. If you have low bandwidth and you have a relatively large repository, say more than one GB, it will take a lot of time. View full review »
Sign Up with Email