CA Service Management, including CA Desk Manager, is a fully-featured ITSM platform, now from Broadcom. It competes with BMC Remedy, ServiceNow, FrontRange ITSM, Cherwell Service Management etc. It is based on technology acquired by CA in 2010 with Nimsoft, and is now supported by Broadcom since the 2018 acquisition.
N/A
Jira Service Management
Score 7.9 out of 10
N/A
Jira Service Management (formerly Jira Service Desk, now including features from the former Mindville Insight, acquired by Atlassian in June 2020) is a service desk software that is purpose-built for IT, service, and support teams. The software provides everything IT and support teams need out-of-the-box for service request, incident, problem and change management. Jira Service Management integrates seamlessly with Jira Software so that IT and development teams can work better together. Users…
$0
per month
Pricing
CA Service Management, with CA Service Desk Manager
Jira Service Management
Editions & Modules
No answers on this topic
Free
$0
per month
Standard
$20
per agent/per month
Premium
$40
per agent/per month
Enterprise
Contact sales team
Offerings
Pricing Offerings
CA Service Management
Jira Service Management
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
CA Service Management, with CA Service Desk Manager
Jira Service Management
Features
CA Service Management, with CA Service Desk Manager
Jira Service Management
Incident and problem management
Comparison of Incident and problem management features of Product A and Product B
CA Service Management, with CA Service Desk Manager
8.6
Ratings
6% above category average
Jira Service Management
8.2
Ratings
1% above category average
Organize and prioritize service tickets
9.70 Ratings
7.50 Ratings
Expert directory
8.70 Ratings
9.00 Ratings
Service restoration
8.40 Ratings
9.50 Ratings
Self-service tools
8.60 Ratings
7.00 Ratings
Subscription-based notifications
7.90 Ratings
10.00 Ratings
ITSM collaboration and documentation
9.70 Ratings
7.00 Ratings
ITSM reports and dashboards
7.50 Ratings
7.50 Ratings
ITSM asset management
Comparison of ITSM asset management features of Product A and Product B
CA Service Management, with CA Service Desk Manager
9.2
Ratings
11% above category average
Jira Service Management
10.0
Ratings
20% above category average
Configuration mangement
9.70 Ratings
10.00 Ratings
Asset management dashboard
10.00 Ratings
10.00 Ratings
Policy and contract enforcement
8.00 Ratings
10.00 Ratings
Change management
Comparison of Change management features of Product A and Product B
CA Service Management, with CA Service Desk Manager
9.1
Ratings
8% above category average
Jira Service Management
7.2
Ratings
15% below category average
Change requests repository
9.00 Ratings
7.50 Ratings
Change calendar
8.60 Ratings
6.50 Ratings
Service-level management
9.50 Ratings
7.50 Ratings
User Ratings
CA Service Management, with CA Service Desk Manager
CA Service Management, with CA Service Desk Manager
Jira Service Management
Likelihood to Recommend
It is a suitable tool for a large organization with extensive user needs. It is not for a small shop as it may be over-engineered for smaller organizations that don't have teams that can manage a solution of this size. It does have some significant hardware and configuration needs, but that should not deter customers from deploying it in-house. I've seen it deployed in the cloud as well as in-house; the downside to deploying it as a hosted solution is you're forever at the mercy of the vendor for customizations, and they cost an arm and a leg. The simplest things take a long time and cost much more money than necessary, so you can't truly get a custom solution and end up with mostly vanilla services (unless you have very deep pockets.)
Great to manage your issues in a clear and centralised way. If your development teams work with Jira, it will all naturally come together. Great way to manage the issues from end to end. - Very flexible if you have people who understands the set up and is able to configure it for your needs - Maybe not the best if you want something with very easy set up
This application is very easy to use. It is the best when it comes to training since the application is easy to understand and employees are able to easily catch up on work process.
It is a great reporting tool because users can look up work they've done over a period of time.
The auto populate feature is very helpful since at the service desk users do have several tickets to create for a single requester.
Linking into other ITSM Tools for automatic event/alert generation could be a good feature to use. Not sure if this has been addressed in later versions of the product.
Effective integration into communication tools such as pagers, text messages would be a great plus. Again this may have been addressed in later versions.
Some of the built-in functions and workflows are surprisingly limited given the fact that you can customize a lot with JQL. These limited areas do not allow you to use JQL. For instance, the built-in notifications are lacking. They have one that is great-- "notify on critical ticket creation"-- EXCEPT that it does not allow you to notify a group or anything, only individual users.
The ticket interface is a little odd for agents. Changing the status is not a simple drop down from unassigned to open to in progress to pending, etc. There are a couple of tabs ("investigate", "pending", "workflow") where you can change the status in different ways. Maybe I am just not used to this way of doing it, but I feel like it could be simplified.
It can get complicated deleting/changing some of the out-of-the-box fields and rules, because you never know what will break workflows or other automated/built-in features.
While the concepts of Service Desk and EITM were solid. The user interface, tool capabilities, and integrations fell behind the rest of the industry. Too often it seemed like CA bought and rebranded products without fully integrated them with their other products. It was a coat of paint, without the parts under the hood being updated. The overhead for administration was too high and the reporting capabilities were absolutely amongst the worst I've seen.
I have given this rating because, in my opinion, I don't see any downsides of Jira until now. We can customise workflows based on the project needs, including task workflows. Jira is very extensible, which is one of its most important features.
I gave JIRA a 9 rating since for me JIRA works according to its purpose. Since there is a customer portal, our clients can leave a comment or communicate with us using the PR ticket that way it is easier for us to also request any additional information we need for our investigation.
We are too integrated with CA Service Desk Manager to disassociate anytime soon. We found the more we used the product the more we needed to customize it in order to better integrate with our business processes. There are other alternatives that have many built-in features that had we have foreseen our future requirements... would have chosen ServiceNow or Remedy as our "go-to" ticketing product.
We chose Jira Service Management due to its easy integrations with the rest of the Atlassian tools, as we have also invested in those. For the price, the ability to add or remove agents, and the cost being reflected in that, it was an excellent medium for us. For the foreseeable future, I do not see us moving off this platform.
Because of the difficulty in creating various functions and workflows, it has had a negative impact over time to where the 'knee-jerk' reaction to any new options requested or desired is to customize it which has resulted in mimicking out of box functions through the customizations.
Examples of the use of certain areas and options is lacking. This has resulted in the misuse of various fields. For example: Multi-tenancy we do not have turned on and was never pursued because we we're told it "wouldn't work for us". This has resulted in previous administrators creating many new roles (which in turn has created just as many access types and data partitions) which has created a large amount of overhead. It's now difficult to turn on multi-tenancy until this overhead can be reconstructed/removed and the bringing personnel up to speed on the changes.
On the initial install (which I wasn't with the company at that time) CA had provided us with custom scripts to execute certain functions (without considering if Service Desk could actually do that function out of box) and applied it. After a few upgrades to the product, these scripts are still being used and have caused underlying issues since their application. CA has denied support on these scripts because they are customizations even though we are looking to remove them.