


JIRA Service Management and OpenText Service Management (SMAX) are competing in the IT service management domain. JIRA is more cost-effective, while SMAX has the upper hand with its extensive features for those prioritizing advanced capabilities.
Features: JIRA Service Management provides integrated collaboration, agile project management, and seamless integration with Atlassian tools. OpenText Service Management (SMAX) offers AI-driven predictive analytics, customizable workflows, and virtual chatbots capable of advanced interactions.
Room for Improvement: JIRA Service Management could improve complexity due to its flexibility and enhance the learning curve of its JQL syntax. SMAX could benefit from reducing its high upfront costs and streamlining manual reporting efforts.
Ease of Deployment and Customer Service: Both JIRA and SMAX offer cloud-based solutions, but JIRA emphasizes easy setup and integration with Atlassian tools. SMAX stands out with tailored deployment options and strong customer support for complex needs.
Pricing and ROI: JIRA Service Management generally has a lower setup cost, providing a budget-friendly option with reasonable ROI. SMAX, with its higher initial cost, offers advanced features that could lead to a higher ROI for businesses needing comprehensive service management.
In terms of cost, we participated in projects achieving two to three million dollars in annual savings.
As a return on investment, we have achieved a 250% ROI in six to nine months, and sometimes it increases up to 380% percent.
Automation Anywhere has helped us save money.
Whenever we need help, we can reach out to them, and they help us out.
We also have dedicated account managers and technical experts to solve our problems related to Automation Anywhere.
We just have to raise a ticket, after which we receive a call, email, or ping from the Automation Anywhere team.
I have reached out to customer support whenever I face an issue in JIRA, especially when creating any automation.
Support for OpenText Service Management (SMAX) is better.
As we are using Microsoft Copilot for our AI agents, I look forward to integrating it with Automation Anywhere and its solutions, seeing it as a beneficial partnership as Automation progresses toward AI as the main solution.
The centralized control room allows us to orchestrate and manage bots seamlessly.
I can scale it in terms of hundreds of bots and configure hundreds of parallel robots easily.
It supports introducing new features or levels efficiently across our global locations, helping everyone stay informed.
JIRA Service Management scales effectively as the number of users, projects, and work items increases.
JIRA Service Management's scalability is excellent; I just need to submit an email to indicate how many licenses I want.
With the latest applications, there are no significant issues like freezing or crashing.
From a stability and reliability perspective, we can remain confident that the product performs as an enterprise solution and meets expected standards.
If you have good best practices, reusable code, an effective framework, and a solid development methodology, bots can be very stable.
There should be more governance for permissions and more options for customized access without frequently involving the admin.
In terms of stability, JIRA Service Management is reliable day-to-day as long as the data is fed in correctly.
JIRA Service Management is stable for my needs; I have not encountered any issues with reliability.
OpenText Service Management (SMAX) has some stability challenges that are crashable and not stable at times.
It is better to write a Python script instead of using Automation Anywhere's package when dealing with Excel because it is buggy and tends to break.
Making the product more lightweight by reducing its dependency on infrastructure could greatly help in the long run.
It would be beneficial if the platform provided options for power developers to integrate seamlessly with languages like Java or C#, allowing them to write their own scripts and code.
JIRA's user interface needs training to understand and utilize.
It remains one of the main barriers to using JIRA Service Management across our entire company.
We need to consider which AI tool would be most suitable for our project.
One important thing we think should be included is a module for metrics, similar to Google Analytics, that focuses on the metrics of the tool usage.
The custom reports that were already prepared work fine.
Different scenarios require different workflow configurations.
It is more cost-efficient compared to all other RPA platforms.
Automation Anywhere costs are aligned with UiPath and Blue Prism, which are also expensive.
It is not cheap, with costs ranging between 700 to 800 dollars per month.
We used Jira's free version for some time.
While licensing is costly, setting up JIRA Service Management is overall good because the vendor helped me, and I also received support from JIRA support, making it a positive experience.
OpenText Service Management (SMAX) is okay, not expensive and not the cheapest.
I can set it up to provide users with a form to fill in all required information, and then the bot operates based on those specifications.
For example, the email module has been enhanced over the years to support all the latest authentication technologies. That is very important as we move away from username and password and embrace multi-factor authentication.
Automation Anywhere has undergone drastic changes over the past five years, transitioning from version 10 to A360, including desktop-based and cloud-based options.
JIRA itself is valuable for managing tickets, user stories, and pipeline.
For every task we are working on, the project manager can see the status once we update the stories mentioned.
It is beneficial if someone is on vacation since others can follow up on the tickets.
Our feedback is that because OpenText Service Management (SMAX) portal is very easy to use, we see customers abandoning their legacy ways of reporting like phone calls and emails, concentrating everything on a portal, which provides end users with more visibility of what's happening because they can control the status of their requests, allowing IT a faster way to intervene and solve issues.
Reporting tools and sophisticated customization options are available with different capabilities.
Configuration is available for different scenarios including change request, incident management, and problem management.



| Company Size | Count |
|---|---|
| Small Business | 154 |
| Midsize Enterprise | 82 |
| Large Enterprise | 536 |
| Company Size | Count |
|---|---|
| Small Business | 30 |
| Midsize Enterprise | 25 |
| Large Enterprise | 34 |
| Company Size | Count |
|---|---|
| Small Business | 3 |
| Midsize Enterprise | 2 |
| Large Enterprise | 4 |
Automation Anywhere offers ease of use, robust system connectivity, and GenAI-driven document automation through a cloud-native platform, significantly enhancing productivity across multiple industries with advanced AI features.
Delivering a comprehensive suite of tools designed for easy integration and rapid deployment, Automation Anywhere drives efficiency by reducing costs and automating repetitive tasks. Its cloud-native platform supports broad industry adoption, including advanced AI features like process automation and Co-Pilot, streamlining complex workflows with minimal technical skills required. Users benefit from robust integration capabilities, which facilitate seamless interaction with multiple systems. However, there is room for improvement in areas such as user-friendliness for beginners, stability, flexible licensing, and enhanced OCR functionality. Organizations in sectors such as banking, finance, manufacturing, and healthcare gain from the improved operational efficiency and ROI Automation Anywhere offers.
What are the important features of Automation Anywhere?
What benefits should be evaluated in reviews?
In the insurance industry, Automation Anywhere is utilized for automating processes such as enrollment management and compliance checks. Its applications extend to supply chain management, financial transactions, and business performance monitoring across sectors like banking, finance, manufacturing, and healthcare, helping organizations to automate routine tasks, improve efficiency, and reduce costs.
JIRA Service Management is recognized for customization, ease of use, and integration capabilities, offering flexible workflows and dashboards that enhance ticket management in organizations.
This platform contributes to streamlining business operations with features like automation and real-time updates. Businesses implement JIRA Service Management to manage ITIL processes, support tickets, and issue tracking both internally and externally. It is utilized for project management and lifecycle tracking, with Kanban boards and Confluence integration supporting change, incident, and problem management.
What are the key features of JIRA Service Management?Service management platforms like JIRA Service Management are integral to industries focusing on managing IT services, such as tech firms and support-focused sectors. Organizations frequently utilize its capabilities to enhance their customer service operations, supporting optimal SLA adherence and efficient query management across departments. By tailoring its application to unique operational workflows, companies achieve improved service delivery and responsive issue resolution.
OpenText Service Management Automation X delivers efficient service management automation with user-friendly configurability across IT, IoT, HR, and finance sectors. It enhances business processes through integrated incident management and natural language processing with virtual chatbots.
OpenText SMAX blends user-friendly design with broad language support and robust storage. It enables organizations to deploy in both on-premise and cloud environments using Kubernetes. SMAX excels in business process improvement, incident management, and uses intelligent agents for autonomous alerts and issue resolution. However, it requires enhancements in integration capabilities and documentation, third-party product connectivity, and contract management. Users face challenges with process automation and search functionality, demanding greater customization and flexibility.
What are the key features of OpenText SMAX?Banks and telecom companies primarily employ OpenText SMAX for service management automation, leveraging its ESM and ITSM capabilities. Deployed on-premise and via cloud, organizations in regions such as Saudi Arabia focus on integrations and upgrades, using SMAX as an end-user portal for incident management.
We monitor all IT Service Management (ITSM) reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.