Bamboo could improve by having compatibility with GitLab. It would be better to have this platform for deploying code and storing container registries. Bamboo does not have a container registry. Additionally, there could be more features added.

Bamboo’s technical support services, in terms of speed of response, need improvement. They should work on providing faster backup replication as well.

One area that could be enhanced is the governance process, particularly with regard to building approvals and transitions between stages. In comparison to other solutions, such as Jira, which features a workflow that supports approval processes, this capability is not natively available in Bamboo. To implement this functionality, integration with other solutions, such as GSM may be necessary. Although some add-ons, such as Adaptavist ScriptRunner, are available in the market to circumvent this limitation, they may not offer the exact functionality needed. Therefore, there is certainly room for improvement in this area.

Currently, Atlassian University does not offer a dedicated course for learning Bamboo. If you wish to embark on a learning journey to acquire knowledge about the solution, your only recourse is to seek out experienced users who are willing to share their expertise on learning platforms like LinkedIn or Udemy. However, this falls short of a structured classroom-based approach, which Atlassian should consider incorporating into their official university platform to provide a comprehensive learning experience for users. However, there is a lot of documentation, but this is not the same as training.

This lack of training might be due to the focus that Atlassian has on the cloud platform rather than on-premise.

The tools and capabilities of the system are extensive. It can be challenging for someone new to the system or ecosystem to grasp, making it difficult to train new people and help them understand.

People know more about Jira than Bamboo. In general, people should know that Jira and Bamboo are similar solutions. The marketing strategy of Bamboo is an area of concern where improvements are needed.

I believe that Bamboo should provide some support as there are too many scripts when we try to do something in GitHub. Every tool has its own style of automation, which is something I would like to be standardized so that the tools become more friendly when it comes to porting so that I can use Bamboo or GitHub Actions freely. I want all the tools to have the same standards, which would help our company.

I feel there is always a scope for improvement in the product's initial setup phase.

Bamboo should provide a permanent free tier, not a time-bound one for startups, as it helps users know if something works well and is utilized or not. Bamboo should offer some permanent free trial for one user or ten users, whatever it is.

We are considering moving to a cloud solution and to use Bitbucket pipeline because of the features it offers. From a hosting perspective, it's easier to make use of solutions that are hosted in the cloud rather than to maintain the tool on-premise. This is not feasible with Bamboo. 

A feature I would like to see added is the integration with quality assurance reports when you run automated tests such as a Selenium test. It would be great to have the results visualised to understand the quality of a build. It is possible to do this manually but it requires a lot of configuration. 

It would be great if Bamboo could introduce a more containerized deployment model. Bamboo should also provide more user-friendly flexibility. For example, if we want to maintain the Bamboo job configuration, we need to export the configuration to Java. However, it would be good if the coding syntax could be simplified.

The performance around the deployment feature could be improved.

Bamboo can improve by providing more with scripting, such as they have with Jenkins. Bamboo is more UI-driven at this time, Jenkins is going in that direction too.

It should be much easier to use. It shouldn't require a lot of reading to be able to use it. It should have just two or three screens rather than hundreds of screens requiring a lot of clicking. It also requires a lot of integration.

It has a steep learning curve. It takes a lot of time to understand and put in the data. There is also no proper training.

The REST API for our deployment project is still very basic and lacks the ability to provide a decent amount of custom automation. For many things, we had to resort to direct database queries simply because certain data was not exposed via the API.

Version control for plans is currently not really possible. This is pretty much the deal breaker for me and why I'm moving away from Bamboo.

The Upgrade process is also clumsy and requires manual steps. I'm not a fan of tarballs.

Bamboo is a bit complicated to use compared to other solutions, such as GitLab. You have to integrate different actions that are difficult that could be made easier.

We are lacking proper support for branched builds using multiple source repositories. The current approach is quite clunky (or non-existent) but it seems there is something in the pipe line for the end of the year according to a recent post on the Bamboo Jira.

• Logging, no integration with Octopus
• Build time variables did not have ability to select from a list of value
• No ability to customize Build version
• TFS plugin had no local workspace editing of checked out files, as all files coming from TFS have read-only attribute turned on by design
• No history view column adjustment
• Password variable values were not concealed within GruntJS logs
• Watching build log GUI loses focus at build completion making debugging difficult
• Mediocre .Net Code Coverage support and reporting.

It's a little outdated. It's three years old. 

There are no areas that need improvement.

• Ease of use.
• It needs "re-build/Trigger build" switch from Stash Pullrequest.
• More 3rd party plugins to support IDEs.
• Integration of older plugins with newer version of Bamboo.
• More options for deployment plans
• Configuring tools to agents (Had to do it manually). It would be nice have sharing from server.
• -Docker support
• Limited options with SSH plugins, can't use options to it

The solution needs to support more customization in the training. What's offered is pretty generic. They need better training and should offer more guidance.