Jira Service Management vs. KACE Systems Management Appliance (SMA)

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

I think it has added value for any organization. It reduced our Tech Support cost by: -Supporting users anywhere -Reducing users downtime as well keep them informed with the status of their tickets -Managing software and hardware actively -Processing automation -deploy mass software installs, patching or updates - Provide approved software's to users to install without IT help

Incentivized

• Manageable workflow to ensure all users follow the same process.
• Can ban boards for easy visual of ticket status.
• Very flexible tool that can adapt to lots of different uses outside of the traditional service desk model.
• Added communication tools help you get out of e-mail jail.

Incentivized

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

Incentivized

• Ability to control the number of email notifications received (Note: this is a new feature in the Latest release but I personally haven not extensively looked at it and how well it solves the existing problem).
• No way to reply to multiple tickets at once, say you got 4 tickets in for the same issue, there is no way you can reply to them in one stroke. Other Ticketing systems do have this ability.
• Using a large number of add-ons to customize and add additional features adds up quickly and can become rather expensive.
• Request forms are very basic and there is no native dynamic field ability available.

Incentivized

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

Incentivized

I gave JIRA a score of 9 since I am happy with the service it offers. I can easily see the SLA since it gives me visibility. I can pull up the reports I need. I can reach out to our clients using the PR ticket so it is hassle-free for me.

Overall, the software is simple to understand and use. That said, most vendors have been slowly updating their user interfaces to HTML5 so that they have a clean updated look and feel. This is where KACE falls short in that the UI is great for a packaged software 10 years ago. This isn't a major limitation as the software is really meant primarily for technology users.

Incentivized

I have not used the technical support from Atlassian. In terms of online help and resources, they are a bit limited thus making it more of a challenge to troubleshoot issues and learn more functionality. There aren't a lot of resources available on the Atlassian site besides developer documents. It would be nice to have a blog or forum where users can get the help they need.

Incentivized

KACE does exactly what you need it to do, it maintains your computer environment. You can set patch schedules, inventory computers, setup software catalogs; basically everything you need to ensure the computers on your network are being actively managed. This is all with little need for constant configuration or updating the setup.

Incentivized

When I evaluated Spiceworks, it was not going to be replacing any ticketing systems. However, I did evaluate it and was not extremely impressed by the short demo I did. JIRA was selected because a branch of our company was already using it, so it made sense to consolidate into one service desk solution, and JIRA was the better option since it was less expensive and geared towards being a ticketing system.

Incentivized

We have selected this software because it rolls several different systems into one. We have a helpdesk system with this and an asset and inventory management system as well. We pay one price for the whole system instead of paying multiple companies different amounts that would have totaled more than we pay for the single system.

Incentivized

• JIRA has been incredibly useful. Our work is more organized and easier to view by the team members as well as upper-level people.
• Our work is correctly assigned and when there are issues, they can be immediately addressed within the tool.
• Users can attach screenshots or files of issues that help clarify the ticket. Developers can attach relevant data as well.

Incentivized

• 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

Incentivized