Jira Service Management (Jira Service Desk) vs KACE Systems Management Appliance

• Highly configurable Notification Scheme, allowing free customization on who receives notifications and when
• Ability to add extra features through the highly diverse Atlassian Marketplace.
• Simple and highly customizable ticket interface. The Software can be almost completely branded in every aspect to represent your organization.
• Integration with Jira Software allows support tickets to be moved into other Log Term projects as necessary.

Read full review

• Inventory: KACE provides a ton of hardware and software inventory information that is easy to search, filter, and export. This is critical when we need to find the answers to questions about how many of such and such we have in our fleet.
• Patch Management: We were using WSUS before and it was altogether too cumbersome. KACE has given us the power, flexibility, and verification we need to feel comfortable our patches are up-to-date.
• Service Queue: We made KACE our help desk system and it does everything we need it to do. Great improvement over our old system.

Read full review

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

Read full review

• The KACE SMA needs a better way to handle different roles in the software so certain users can access or administrate certain parts of the software, but not the entire software installation.
• The KACE SMA could improve the ticketing process of projects. The aspects of the title and some information do not always flow down from the parent ticket to its child tickets.
• The KACE SMA could improve the UI of the software with the addition of different CSS color schemes.

Read full review

• We would not be very organized as a software company without using JIRA and it would in turn reflect negatively across the entire studio and the products that we release.
• Almost everyone in our company uses JIRA in one way or another from developers to testers to marketing and every team in between.
• The only time I have witnessed that JIRA has a negative effect on our objectives is if they suffer a major failure on their part and JIRA is not accessable or usable for a length of time. Thankfully in over 3 years of using JIRA this has only occurred a handful of times.

Read full review

• KACE has saved us from having to spend several days of employee hours in crafting DVDs and duplicating them (100+ DVDs)
• KACE has saved us on the postage required to send out those DVDs for every update (monthly) to all of our customers electronically

Read full review