EasyVista Service Manager vs. Jira Service Management

It is well suited for a service-based department, but it can sometimes offer confusion for non-technical users because of the amount information the form fields require. Most customers don't want to write the equivalent of a book to simply say that " I want to obtain a license of Adobe Acrobat and charge it to the department."

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

• Documentation is very important for any technology department. We can easy attach quotes, screenshots of issues, or invoices so that any one looking at the work order once closed can see that the task was completed quickly or may require more resources if needed again.
• Tracking the progress of your team is also important when considering pay scales or promotions. Reports help you see which employees are going above and beyond and those that are needing extra motivation.
• Universities have to work as cohesive unit to be successive. Our customers tell is us what is needed for them to do their jobs and we are able to divide the work amongst our staff to continue the quest quickly.

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

• Customization without the need for lengthy contacts with tech support. Non-technical team members should be able to resolve malfunctions with the interface and its components.
• A mobile app would make resolving work orders in the field easier. Without the need for a PC-like device to access the program. Many times, weather conditions are not kind to tablets. A cell phone is more reasonable.

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

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.

There has been less downtime due to incompatible upgrade elements in our environment. EasyVista is takes hours not days to troubleshoot and resolve any functionality errors. Tech Support has been more helpful and reachable.

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

• Our turnaround time has decreased steadily use implementing use.
• Our CIO is update on the progress of his team at all times.
• The customers feel better informed about their requests from start to finish.

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