Codebeamer Reviews

My feedback on Codebeamer is that we are using it to store codes that are working on a functional level. Most of our employees are working in Codebeamer for the Kanban board, and we are organizing our organizational structure. For example, we have established a hierarchy from manager to manager within Codebeamer. These are the things we are doing with Codebeamer. It is working fine despite being older, and our organization prefers Codebeamer, although other people are also working with GitLab alongside it.

We are currently working with Codebeamer version 2.2. Just a few days before, we completed an update in Codebeamer, and our organization keeps updating things.

Other benefits observed from using Codebeamer include its excellent release management and access management features. For example, we have employees and some admins, and the admin can give access to others similarly to AWS. Certain features can only be performed by admins, which allows for flexible assignment. For instance, we can assign access to a developer group, enabling the entire development team to engage in tasks such as adding and pushing code.

The most valuable features of Codebeamer that I found are the release management and sprint management. In our organization, we work on a sprint basis using Agile methodology, so each sprint we declare one Kanban board in our sprint planning meeting or in retrospective, which is helpful. The Kanban board and release management are especially beneficial.

The integrations with Codebeamer have helped streamline a software development process in our company, especially as our company is developing some AI tools in a newly developed department. Recently, they needed to run some test cases and requirements on demand, and through Codebeamer, we can put the code and trigger it via the API whenever needed, allowing for on-demand runs of test cases. Most people are also storing code for specific requirements to share with others, and we are using Codebeamer as well as GitLab; some people prefer Codebeamer while others prefer GitLab.

Everyone is using Codebeamer's reporting tools, so we leverage its advanced analytics and reporting capabilities.

I find Codebeamer to be best suited for automotive projects in various automotive companies. It is very economical for medium-sized companies. It finds use cases in small, medium, and large enterprises. However, I strongly recommend it for medium companies.

The key features of Codebeamer include templates and basic structures, most of which are created and readily available for deployment out of the box, reducing deployment time. Additionally, its integration capability is very high, with almost eighty to eighty-five percent of integrations available readily out of the box, minimizing the need for specific integration-related work.

We are using Codebeamer and the whole V-model for requirement change, task management, and issue management.

The primary challenge is adapting the standard product to our workflows and specific needs. We are currently working on or have challenges to solve with PTC. Codebeamer is user-friendly, but we have issues with some specific topics.

We use CodeBeamer to understand tools and map all the business requirements.

During migrations from other platforms to CodeBeamer, there have been instances where we encountered issues that required redoing certain tasks.

We primarily use the solution for lifecycle management, or ALM, including task management and HR planning.

I like the integration with everything.

The solution is stable.

It's easy to set up.

There is a lot of complexity involved, meaning it can do many things, which can be quite useful.

We use Codebeamer to manage software in our automobile business, for entire project management, and the CI/CD cycle.

Codebeamer's API-based integration and many other integration aspects with other solutions are very powerful.