Ivanti Neurons for ITAM vs. Jira Service Management

Ivanti ITAM suite is very robust and offers all the features you need in an ITAM solution. Out of the box, you get all you need, but you are able to customize and add processes that are missing very easily. It will work for any organization, regardless of complexity. We have the full suite of Ivanti products and there are nice integration options that make usage very seamless.

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

• Remote PC Inventory
• Remote PC access (PC access)
• Reporting
• Offsite PC access (through LANDesk Gateway)

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

• Licensing can be complex and is fairly expensive. I did not research other ITAM solutions as we use the entire Ivanti suite to see how pricing compares, but it does seem expensive.
• Be careful when you are building you CMDB module in the Ivanti Service Desk tool, we found the hard way that create custom CI processes requires an ITAM license.
• We have submitted a few bugs and the resolution from support seems slow. I find this is common with many vendors, but was hoping for better resolution times with Ivanti.

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.

This is the only software suite in its category I have any real professional experience with, so I cannot speak to how it stands up to the competition

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

• We have seen tremendous ROI with custom processes set up to manage the lifecycle of our assets. This was a huge void for us previously and now we can see when assets are coming/going and when they should be retired.
• Integration with other apps via API has allowed us to automate manual tasks and streamline processes.
• Tie-ins with the CMDB function of Service Desk have allowed us to create dynamic workflows to manage the lifecycle of assets and other related assets. Very powerful use case.

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