AutoRABIT Automated Release Management (ARM) could be improved by offering the feature where I can deploy both OmniStudio and Salesforce components together.I would also mention that the UI should be more user-friendly. Rather than displaying all code, it should have a better user interface.
Senior Sales Force Developer at a tech vendor with 10,001+ employees
Real User
Top 20
Jun 3, 2026
I would say syncing up with Jira for AutoRABIT Automated Release Management (ARM) could be improved. We have the stories and are picking the PR links directly from Jira. We tried this in our project, but it was not seamless connectivity, so we were not able to implement it fully. It would be helpful to have some customization after the PR is taken from Jira and deployed through AutoRABIT Automated Release Management (ARM). For example, automatically updating the status back to Jira would be beneficial. We need some customized statuses, which would be helpful for us. I can say there are some other opportunities where AutoRABIT Automated Release Management (ARM) could improve. I need to explore where we can make further use of it. Due to that, I have given that score.
To improve AutoRABIT Automated Release Management (ARM), I suggest adding components such as managed packages and velocity components, which could also be deployed, and it could connect with multiple orgs using SFDX metadata instead of the old metadata, which would be helpful for Salesforce development.
Certain improvements that I feel should be made would start with the UI perspective. The UI is not user-friendly, and newcomers or new users might get confused at times about how to proceed and what to do. This is an area AutoRABIT Automated Release Management (ARM) should work on. Additionally, the build and deployment job configuration is very powerful but complex. There are many settings, and the consequences of misconfiguration are not always clearly communicated until a deployment fails. We have also experienced occasional performance issues with the web application during periods of high concurrent activities, particularly when multiple teams are running deployments simultaneously. During those times, we feel lag. Regarding needed improvements, deployment progress visibility when we kick off a large metadata deployment involving hundreds of components is quite limited. There are times when it is genuinely difficult to tell whether the deployment is progressing normally or has silently stalled somewhere in the middle. A more granular real-time progress view would reduce a lot of anxiety during critical deployment windows. I would also mention the observability integration. We heavily use DataDog for monitoring our systems, and there is no clean native integration between AutoRABIT Automated Release Management (ARM) and DataDog. This means deployment events are completely disconnected from our application performance metrics, so correlating a deployment with a spike in errors requires manual cross-referencing between two separate tools. A proper webhook or native integration would be a significant improvement.
Learn what your peers think about AutoRABIT Automated Release Management (ARM). Get advice and tips from experienced pros sharing their opinions. Updated: June 2026.
AutoRABIT Automated Release Management (ARM) streamlines software delivery with its seamless integration, providing a robust platform that boosts team efficiency while managing complex development pipelines.AutoRABIT ARM is designed to accelerate release cycles and maintain code quality by offering features such as deployment automation, version control, and environment management. Its comprehensive toolset enables DevOps teams to coordinate effectively, minimize errors, and ensure compliance...
AutoRABIT Automated Release Management (ARM) could be improved by offering the feature where I can deploy both OmniStudio and Salesforce components together.I would also mention that the UI should be more user-friendly. Rather than displaying all code, it should have a better user interface.
I would say syncing up with Jira for AutoRABIT Automated Release Management (ARM) could be improved. We have the stories and are picking the PR links directly from Jira. We tried this in our project, but it was not seamless connectivity, so we were not able to implement it fully. It would be helpful to have some customization after the PR is taken from Jira and deployed through AutoRABIT Automated Release Management (ARM). For example, automatically updating the status back to Jira would be beneficial. We need some customized statuses, which would be helpful for us. I can say there are some other opportunities where AutoRABIT Automated Release Management (ARM) could improve. I need to explore where we can make further use of it. Due to that, I have given that score.
To improve AutoRABIT Automated Release Management (ARM), I suggest adding components such as managed packages and velocity components, which could also be deployed, and it could connect with multiple orgs using SFDX metadata instead of the old metadata, which would be helpful for Salesforce development.
Certain improvements that I feel should be made would start with the UI perspective. The UI is not user-friendly, and newcomers or new users might get confused at times about how to proceed and what to do. This is an area AutoRABIT Automated Release Management (ARM) should work on. Additionally, the build and deployment job configuration is very powerful but complex. There are many settings, and the consequences of misconfiguration are not always clearly communicated until a deployment fails. We have also experienced occasional performance issues with the web application during periods of high concurrent activities, particularly when multiple teams are running deployments simultaneously. During those times, we feel lag. Regarding needed improvements, deployment progress visibility when we kick off a large metadata deployment involving hundreds of components is quite limited. There are times when it is genuinely difficult to tell whether the deployment is progressing normally or has silently stalled somewhere in the middle. A more granular real-time progress view would reduce a lot of anxiety during critical deployment windows. I would also mention the observability integration. We heavily use DataDog for monitoring our systems, and there is no clean native integration between AutoRABIT Automated Release Management (ARM) and DataDog. This means deployment events are completely disconnected from our application performance metrics, so correlating a deployment with a spike in errors requires manual cross-referencing between two separate tools. A proper webhook or native integration would be a significant improvement.