Jira Service Management vs. Kaseya VSA

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

If the software functioned as it was intended, it would be probably a 7 out of 10. It lacks the majority of customization that SolarWinds N-central supplies, but also supports some customization that other solutions we have tried do not. Again, if the software didn't consistently break, the ability to implement automated scripting via PowerShell and the capacity to manage 10+ endpoints at once in different windows is great.

• 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

• Being able to see systems that are not within the local network allows us to be able to troubleshoot and work with the end users no matter where they are or where we are as it is cloud based.
• Several functions can be "automated" so staff do not have to keep going back and scanning for updates, push Windows updates and or push sensor updates.
• VSA offers a variety of system information about all of the assets that have the endpoints installed on them so we can easily see the system specs without having to actually connect to them and pull up the SysInfo on each unit.

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

• Support - Like all other competitors support is OK but the product is robust enough to reduce support requirements.
• Customer Service - another team that is a bit poor especially when the issue involves multiple departments. Otherwise, the direct rep is very friendly and professional.

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

Excellent product with easy learning curve

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 think this is a solid tool for enterprise IT, however it would be higher if Kaseya VSA addresses the areas raised around recent stability, their support team, multiple session & screen support etc. It does do it's main job and allows an easy way for IT to operate and is mostly fine.

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.

It was lots of back and forth email communication whenever I tried to solve my connection issues. I would send them detailed logs of the date, time, computer, and more of when I was experiencing connection issues. All I would get is an email back a few days later saying that they didn't find an issue in the service

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

There are other products that do some of what Kaseya does, but I've not personally worked with another product that does everything Kaseya does. Sure there are plenty of remote control products, but products that do as much as Kaseya are few and far between. Hard to go wrong with the sheer scope of functionality!

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

• It has increased the efficiency of operational tasks for our technicians
• It has change the speed at which we are able to deploy updates and software patches
• It caused us to spend additional money on more security tools due to concern from breaches

Incentivized