Section Manager at a manufacturing company with 10,001+ employees
Real User
Top 5
2025-08-21T09:54:03Z
Aug 21, 2025
There are absolutely things that could be improved in collaboration features in Bitbucket Server, with respect to people who are not using it every day, such as managers who need to be able to approve things but don't use Bitbucket Server so often. Collaboration could be improved as the main aspect.
Head of Engineering - Consumer Finance at DBS Bank
Real User
Top 10
2024-11-28T07:15:00Z
Nov 28, 2024
While Bitbucket Server performs well, the improvement lies not in the tool itself yet in the discipline of the team using it. The tool does not impose restrictions, allowing for flexibility in workflow management. There might be further integration ideas for continuous deployment.
Bitbucket can improve in several key areas to enhance its user experience and functionality. One significant area is the code review experience. Currently, the interface could benefit from a more sophisticated code viewing option. Introducing a code color theme similar to what is available in Integrated Development Environments (IDEs) like VS Code would greatly enhance readability during code reviews. It would allow for highlighting keywords, making scanning and comprehending code easier. It provides several pipeline examples, but notable limitations exist, particularly regarding the number of pipeline minutes allocated to users. This constraint often forces users to rely on their on-premises servers instead of using Bitbucket Pipelines. Additionally, Bitbucket Pipelines currently do not offer any unique features that set them apart from other Continuous Integration/Continuous Deployment (CI/CD) solutions. Compared to alternatives such as GitHub Actions, Bitbucket Pipelines may appear less competitive due to its lack of distinctive functionality.
The user experience is tedious and long-winded. It could also be smoother from an admin's perspective. Finding settings or working with it is also a bit slow and not very intuitive. The main limitation of Bitbucket Server is the lack of certain features. Many basic features are missing and must be supplemented through the Atlassian marketplace. Additionally, Bitbucket Server lacks support from third-party applications and tools.
I don't see any complexity involved in the product, especially since some of its users are DevOps engineers. My company works less in the area of storing source codes using the product. My company mainly works in the integration area, after which we design and provide the guidelines for new branching strategies. The response time of the product's support team may not be good enough to meet the expectations of users, making it an area where improvements are required. It would be nice if users had the option to download a build directly from Bitbucket in the future.
The product interface consists of multiple features that are complicated to navigate for new users. They could make it easier to access and introduce templates with sample code for beginners to understand Kubernetes deployment.
Quality Assuarance Lead at a marketing services firm with 1,001-5,000 employees
Real User
Top 10
2024-01-12T06:35:49Z
Jan 12, 2024
The solution's user interface could be improved because it's not very user-friendly or intuitive. It feels like old HTML blocks were used to build the user interface. Some supporting documentation for Bitbucket Server would be helpful because it's not very easy to get information about it. I remember having to Google a few times to figure out how to do something on Bitbucket Server.
Founding Member at a tech services company with 51-200 employees
Real User
Top 5
2024-01-11T11:36:34Z
Jan 11, 2024
There’s no integration of the tasks defined in Bitbucket that go to Jira. We define the task on Jira and then connect it to Bitbucket. The task or the issues defined on Bitbucket must be transported to Jira. The tasks on Bitbucket must be automatically integrated into Jira.
There are instances when I interact with Bitbucket and encounter a situation where I've pushed changes to the website server. However, when I access my branch on the website server, I notice that the changes are not immediately reflected. Enhancing the real-time reflection of changes online is an area that could benefit from improvement.
We had issues in terms of logs, URLs, and cloning the repositories, which is the same issue we keep facing in our company though we manage to resolve it each time. The aforementioned problems make the solution a bit tricky, so it would be great if Bitbucket could provide users with a smoother approach or process when they face an issue. At the moment, there are not many details on how to proceed with the troubleshooting if one of the users faces an issue with the product.
DevOps Engineer at a manufacturing company with 10,001+ employees
Real User
2021-04-03T08:34:05Z
Apr 3, 2021
It would be useful if we were able to work and manage other tickets; for example, if I were to use Jira, Confluence, or Bitbucket, all from a command-line standpoint, in addition to the web interface, it would be incredibly helpful. I know that there are tools, packages, and different plugins that I can use to collaborate from a command-line standpoint, or through other tools, but putting the functionality into a new version would definitely help. Some of the capabilities that I am looking for from a command line are not really available.
DevOps Specialist, Release Automation and Deployment at TD Insurance
Real User
2019-07-22T12:52:00Z
Jul 22, 2019
Instead of providing only raw features and plugins, Atlassian should provide a ready-to-use integration of both choices to incorporate "trunk-based" development. For example: * JIRA / Bitbucket / Bamboo or * JIRA / Bitbucket / CloudBees-Jenkins
Bitbucket Server offers seamless integrations with tools like Jira and Jenkins, a user-friendly interface, and robust code collaboration features. It's known for excellent development support, scalability, and high availability, making it a preferred choice for many technical teams.Bitbucket Server stands out due to its flexibility in workflows and ability to manage branching and code integration. It supports pull requests, private repositories, and is easy to manage on servers. Integration...
There are absolutely things that could be improved in collaboration features in Bitbucket Server, with respect to people who are not using it every day, such as managers who need to be able to approve things but don't use Bitbucket Server so often. Collaboration could be improved as the main aspect.
While Bitbucket Server performs well, the improvement lies not in the tool itself yet in the discipline of the team using it. The tool does not impose restrictions, allowing for flexibility in workflow management. There might be further integration ideas for continuous deployment.
Bitbucket can improve in several key areas to enhance its user experience and functionality. One significant area is the code review experience. Currently, the interface could benefit from a more sophisticated code viewing option. Introducing a code color theme similar to what is available in Integrated Development Environments (IDEs) like VS Code would greatly enhance readability during code reviews. It would allow for highlighting keywords, making scanning and comprehending code easier. It provides several pipeline examples, but notable limitations exist, particularly regarding the number of pipeline minutes allocated to users. This constraint often forces users to rely on their on-premises servers instead of using Bitbucket Pipelines. Additionally, Bitbucket Pipelines currently do not offer any unique features that set them apart from other Continuous Integration/Continuous Deployment (CI/CD) solutions. Compared to alternatives such as GitHub Actions, Bitbucket Pipelines may appear less competitive due to its lack of distinctive functionality.
The UI could be enhanced.
The improvements in the product could be made to expand third-party integrations and enhance support for open-source projects.
The user experience is tedious and long-winded. It could also be smoother from an admin's perspective. Finding settings or working with it is also a bit slow and not very intuitive. The main limitation of Bitbucket Server is the lack of certain features. Many basic features are missing and must be supplemented through the Atlassian marketplace. Additionally, Bitbucket Server lacks support from third-party applications and tools.
I don't see any complexity involved in the product, especially since some of its users are DevOps engineers. My company works less in the area of storing source codes using the product. My company mainly works in the integration area, after which we design and provide the guidelines for new branching strategies. The response time of the product's support team may not be good enough to meet the expectations of users, making it an area where improvements are required. It would be nice if users had the option to download a build directly from Bitbucket in the future.
The product interface consists of multiple features that are complicated to navigate for new users. They could make it easier to access and introduce templates with sample code for beginners to understand Kubernetes deployment.
Bitbucket Server can experience performance issues when pushing a large amount of code. This process may take a considerable amount of time.
The solution's user interface could be improved because it's not very user-friendly or intuitive. It feels like old HTML blocks were used to build the user interface. Some supporting documentation for Bitbucket Server would be helpful because it's not very easy to get information about it. I remember having to Google a few times to figure out how to do something on Bitbucket Server.
There’s no integration of the tasks defined in Bitbucket that go to Jira. We define the task on Jira and then connect it to Bitbucket. The task or the issues defined on Bitbucket must be transported to Jira. The tasks on Bitbucket must be automatically integrated into Jira.
Bitbucket Server has limited user support for its free version. It is expensive.
I don't have many complaints from the developers' project.
There are instances when I interact with Bitbucket and encounter a situation where I've pushed changes to the website server. However, when I access my branch on the website server, I notice that the changes are not immediately reflected. Enhancing the real-time reflection of changes online is an area that could benefit from improvement.
We had issues in terms of logs, URLs, and cloning the repositories, which is the same issue we keep facing in our company though we manage to resolve it each time. The aforementioned problems make the solution a bit tricky, so it would be great if Bitbucket could provide users with a smoother approach or process when they face an issue. At the moment, there are not many details on how to proceed with the troubleshooting if one of the users faces an issue with the product.
It would be useful if we were able to work and manage other tickets; for example, if I were to use Jira, Confluence, or Bitbucket, all from a command-line standpoint, in addition to the web interface, it would be incredibly helpful. I know that there are tools, packages, and different plugins that I can use to collaborate from a command-line standpoint, or through other tools, but putting the functionality into a new version would definitely help. Some of the capabilities that I am looking for from a command line are not really available.
Instead of providing only raw features and plugins, Atlassian should provide a ready-to-use integration of both choices to incorporate "trunk-based" development. For example: * JIRA / Bitbucket / Bamboo or * JIRA / Bitbucket / CloudBees-Jenkins