CA Service Management, with CA Service Desk Manager vs. Jira Service Management

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.)

Incentivized

I think using a ticketing system is very easy to use and allows multiple teams to create help desks in the same portal. In terms of internal usage, I think this is a great option. However, suppose you're trying to keep internal items and external helpdesks in the same instance. In that case, this is not ideal, as there is no effective way to separate the two instances to protect internal data better.

Incentivized

• A large community where, if help is needed, is usually very helpful and quick to respond.
• Various sites with good information on various issues. If you have a problem, there's a good chance some else already had it and documented it.
• Fairly easy installation of the product if recommendations are followed and prep-work is done.

Incentivized

• Integration with many of the most common tools companies are using (Slack, MS Teams, Salesforce, ... etc)
• Natural workflow with Jira (as product development / project management tool) which makes the full fix and follow up of the tickets / issues very easy to follow
• Allow multiple different entry points and work flows for as many different needs your teams / company have

• The right-click feature is disabled in this application and users are unable to copy and paste with mouse or touchpad.
• The application also freezes quite a bit and a user will have to quite often close and reopen browser to get it functioning properly.

Incentivized

• Navigating through issues outside of a kan ban board can be confusing and task heavy.
• It's easy to clutter up the tool. It could use some easy clean up capabilities.
• User interface is decent, but could use work to make it more intuitive.

Incentivized

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.

Incentivized

In the current contect the requirments is around having a tool that is focused and can handle large ticket volumes and tracking incident, problem and user requests concerning end users. Jira has built in functionality to address the above practice needs faily easily and has a substantial amount of customizable reports for generating the relevant intelligence.

Incentivized

If you're used to other tools in the Atlassian ecosystem, you'll feel right at home with JSM. It's also a platform that technical folk can easily pick up. However, I wouldn't recommend using JSM as a company's first jumping off point into Atlassian. There are a lot of other 'newer' tools that provide sleeker ITSM systems at a similar cost.

Incentivized

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.

Incentivized

Zendesk is a similar ticketing system that our organization used before JIRA Service Desk. The main drawback of Zendesk was that it can only be used as a cloud service. This means that our company data would be living on the internet at the hands of their security team. Another drawback of this is the price is significantly more expensive rather than hosting it yourself. Zendesk does have some additional features such as commenting on multiple tickets at once that JSD does lack. However, switching to JSD was significantly more cost effective because we have the ability and the infrastructure to host our own ticketing system, something that Zendesk could not provide. Ultimatley switching to JSD saved us money and allows the ability for integration with all of the other Atlassian Suite products that we use on a day to day basis.

Incentivized

• Having CA Service Desk Manager within the company has increased the satisfaction of customer service from 68% to 95%. Teams are getting better customer survey scores and making better efforts to meet their SLAs.
• CA Mobile app has provided agility and collaboration among IT Users and Customers.

Incentivized

• It is definitely cheaper than Salesforce
• It allows the IT service desk to be more organized and respond more quickly to tickets, which can save time for both agent and requester.
• Some things are "not quite there" developmentally, so this means that internal IT will need to spend more time developing and testing the product.

Incentivized