Actually, I have an E-commerce product on that solution and store it there. I deploy the product for each customer and they use it. I'm trying to use the cloud system as my center for distribution. I use Bitbucket for hosting the core code.
I'm using the private cloud because I don't want to have my source public on the internet. I'm very happy about that solution because it's precisely enough for me and my needs. Being private was very important for me, and working with the product's GUI user interface is a good experience.
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.
This solution is perfectly stable. We never had a problem with it, and after five years it is still running as we expect. I love this program for that.
Many software companies are trying to scale up on the cloud. BitBucket should add some features to make some better use of the cloud and other integrations. For example, if you want to migrate your product to AWS (Amazon Web Services), the AWS will try to send the source code to a codecomp system. Maybe you have something that you do not want to migrate from the source to Amazon. It would be nice to have controls for that. When you commit the code to BitBucket it would be good to be able to also commit from BitBucket to use AWS.
In our company, we had ten proficient programmers working on the project and we have good clients in Turkey. We could scale the program as well as the number of users and our market or in other ways. I think I am confident in that. So the product is scalable in many ways.
The company can improve access to technical support. Some of the documentation was not so good. We did not use it much.
From my point of view, the setup for the Atlassian product was better than other products but had less to offer as a system. I tried to switch to TFS (Team Foundation Server), a Microsoft product, and I couldn't use that because I loved this user interface system in the BitBucket product more than TFS.
The first upload of our project was in 2015. I uploaded that code. It wasn't very hard to use the solution or do the deployment. Some of the configuration is not as easy or as good as it could be. The system has changed, but since the implementation, I have made no changes in three years.
In a way, I did evaluate other options but it was after I was already working with BitBucket. I tried to use TFS and GitLab, but I couldn't add my existing support to their systems. I loved this support system that I had with BitBucket — the system was very good. But looked at other solutions because I wanted some other features that these other products claimed to have, like issue tracking and a better wiki. These were things which I couldn't get directly in the BitBucket service. But I had gotten used to the excellent GUI in BitBucket and thought it was almost perfect. There were some things missing but the solution was perfectly enough for us. I decided there was no need to change to TFS or the GIT system after the comparison.
On a scale from one to ten, where one is the worst and ten is the best, I would rate this product as an eight. I love this product, so actually eight may actually not be good enough for the rating. On the other hand, there is a lot that could be incorporated or improved.
