A few challenges have been encountered, and from my experience, Digital.ai Release should improve the user interface. It has a lot of functionality, but some areas can be a little too complicated compared to others, especially when setting up more advanced release flows. A cleaner and more intuitive interface would make it easier to get started and begin using it. I would also like to see stronger reporting and analytics to help track releases, progress, and have ready-to-use reports around deployment success rates. Another area is integration, as Digital.ai Release connects with many DevOps tools, but some integrations can require configurations and maintenance, making the work hectic. If those connections could be made more straightforward, it would save time.

To improve Digital.ai Release, I think the user interface could be improved. For example, I have a plan phase before my build phase, and sometimes the toggle button is hidden. I have to toggle it before the step can be executed, or it will be skipped. Many people who did not use Digital.ai Release before do not even know there is a toggle button, and the first time when they run into that phase, they will definitely skip that step.

Regarding needed improvements, I did not do extensive reading on documentation or training material directly from Digital.ai Release. My knowledge comes from the team who has been using it. However, I would appreciate standardized training material that would give me hands-on experience.

Digital.ai Release could be improved, particularly because the automated test capabilities are not that strong compared to some major tools like UIPath, Tosca, or SmartBear TestComplete. Finding elements, the list of assertions, or the usage of AI to automatically generate test cases based on requirements did not work entirely flawlessly for us, and we have found issues with these features.

Regarding Digital.ai Release's AI capabilities, we have not explored a lot regarding governance and security, as we have only explored mobile manual test management and automated test management. There are definitely other areas where Digital.ai Release could improve, such as workflow management, which UIPath has very good capability for. There is also support for desktop test automation, which I think can definitely be improved. Speed-wise, if you compare Digital.ai's automated testing solution with Cypress or Playwright on web applications, they are very fast and run cross-browser with parallel test execution. I think those aspects can be improved in Digital.ai test automation, along with better integration with tools. I have not seen Jira integration, but other commercial tools have extensive integration with CI/CD pipelines, documentation tools, defect management tools, and test management tools. There are also integrations with Slack, Google Chat, and emails—areas where Digital.ai can also improve.

Digital.ai Release can be improved by reducing the number of tasks that need to be completed before starting a release, as there are too many tasks to get done.

The interface of Digital.ai Release can be improved as well because on first use, you will feel a bit lost, so we could work on the interface to make it easier to navigate.

One improvement for Digital.ai Release could be to simplify the user interface for beginners. New users may take time to understand release pipelines and templates, so more guided onboarding tutorials and documentation would help them adapt easily.

I would suggest documentation and tutorials as needed improvements for Digital.ai Release.

As I do not work much on the configuration of the templates because I am just a consumer, I do not see much improvement required, as it looks good to me.

I am not certain about further improvements since I have not used the template settings; however, I feel that it could be more user-friendly, as the UI feels a bit old and not very appealing. Additionally, to see the logs is challenging because we need to open multiple windows, and it does not display in full screen, which could definitely be improved.

Sometimes it can be tedious when fulfilling multiple different packages with their key and value pairs. If we make any mistakes in the second step and return to the first screen, everything is erased, so there is no way to return to the first screen and start again with the same package or make small updates or changes to the initial screen before restarting the process.

Digital.ai Release is very helpful in saving time, but I wish there was the possibility to use the API as a release manager to automate pre-filling the pipelines.

If we had an API that could be used on the user side, similar to the one in JIRA where we can create a personal token without granting full access to Digital.ai Release, I could have my script automate the process instead of fulfilling the template field by field, which would be excellent.

I chose eight out of ten because I see it is a nice tool. I do not know it in depth to give a higher or lower rating at this point, but for my use and role, I appreciate the parts of the tool I am familiar with. We could have some small enhancements, such as being able to go back to the first screen while keeping everything filled in, but beyond that, I do not have any other suggestions.

Based on my experience, I would like to improve Digital.ai Release by exploring its cloud capabilities as we are currently in the middle of migrating to the cloud, but I actually have no idea what Digital.ai's cloud capabilities are.

As for additional functionality I would like to add to Digital.ai Release, I can't comment on that at the moment, but I think plugins for other deployment tools such as PDQ Deploy, which we use for Windows applications, could make my life easier.

The solution is a little bit expensive. 

There are many areas of improvement. Currently, we put artifact details manually. What we could improve, in our case, is the deployment instruction base. Developers input all the information, including which artifact and where it needs to be deployed. What Digital.ai could do is automatically go to the deployment instruction page, take those artifact details, and implement them. This way, there would be no need to manually input the details.

Digital.ai Release could improve by having a better plugin that works with Guardian that we use for mainframe migrations. If there could be an interface or plugin for Guardian that would be beneficial.

The backfill could be improved, we could automate that. Right now it's subjective — it's up to the lead developer's memory to remember to backfill. 

Overall, the price is just too high; especially considering we're in the middle of a pandemic.

There's definitely some overkill in these products. To me, they seem to be just a little over-complicated — I think they could skinny it down. It's just based on how many users so I don't know if the different roles are priced differently. The DevOps people might be in it a lot more than a lead. I don't know if pricing by role can be different.

If I've got a manager that just wants to go in and audit it, does that person have to have a full license, or is it just a read-only and it's a nickel or something?