We performed a comparison between Device42 and JIRA Service Management based on real PeerSpot user reviews.
Find out what your peers are saying about ServiceNow, BMC, Freshworks and others in IT Asset Management."The solution is agentless."
"The Insights+ component is useful for us because it does business application mapping and helps us visualize it. It saves us time because we don't have to hunt for data."
"The solution has some very good relational capabilities that show us how certain devices relate to each other and how some of our environment actually works together."
"It has agentless discovery; you don't need to put agents on your servers. You can open one or two ports to discover all your infrastructure."
"A big plus for Device42 was the auto-discovery. With it, we have updated devices, updated systems, and up-to-date systems."
"I like the tool's agentless discovery feature. The tool configures the devices based on the documentation provided. I am also impressed with its auto-discovery feature. The tool also keeps on tracking and finds whatever is in the environment."
"They've also just created some new interactive dashboards. CEOs can see and interact with the data rather than scrolling through endless Excel worksheets to find what they need."
"The auto-discovery is brilliant. You can have it scheduled to run on a regular basis, and the infrastructure is always getting updated within the platform. I would rate the asset discovery very highly. It's very comprehensive. It covers quite a lot of different methods for doing discovery and it supports a lot of different types of hardware as well."
"The most valuable features of this solution are Incident and Request Management."
"The most valuable feature of JIRA Service Management is a plugin we are using for the front end for simple user forms."
"It scales well."
"The most valuable feature of this solution is that it is user-friendly."
"Auditing team uses this solution to track audit findings and follow-up."
"This service management solution has a good user interface. It helps improve your IT request requirements and makes tracking requests easier."
"With Jira Service Desk, the simplicity of setting up a quick form and getting the service desk running quickly is very helpful."
"In Jira Service Management, the most beneficial features are process improvement, workflows, and escalations."
"The solution’s automatic IT asset discovery and inventory functionality functions pretty well. There could be some improvement if there were some automated scripts to get it off the ground. I know it takes a bit of effort to get all of various managed devices into one place. We have to go and change how they are managed and make sure they are all linking up correctly so they can be tracked in Device42. Some type of automated script for each to get over that initial activation."
"The architecture is a bit old-fashioned. Device42 is on one server, appliance, virtual machine, or guest. We are loading more into Device42 than it can hold. Overloading Device42 with REST API calls or tasks will directly impact every aspect because the server will be too busy to answer requests."
"Currently, if you want to ping devices, you need to log into Appliance Manager. This feature should be available on the Device42 side. You should be able to use the ping utility without logging into Appliance Manager. The features that are there in Appliance Manager should also be available on the main Device42 server so that you have more control on one screen. You don't need to switch to another portal, but it is not something critical."
"A con for Device42 is that Kubernetes integration is lacking. You pay for 10,000 spot licenses and if you're spinning up a Kubernetes cluster, or four or five or six Kubernetes clusters like we do, you're going to have 5,000 or 6,000 nodes in each of those, doing different types of business things."
"In my experience I believe that the key concern is the pricing strategy of the solution. Instead other solutions such as lanweber are much more cost effective. Previously, Device42 operated on perpetualysis without any fees. But recently they have altered the pricing model to include a subscription fee which I see as a very costly affair. Therefore I would like to suggest that they evaluate their pricing strategy and licence scheme, conduct a market research and ensure that they provide the right product in the market at the right price."
"My biggest problem with the product is the upgrades. First, we have to do them manually and second, not this last time but the time before that, we actually had to build a new VM to deploy the solution again. We had to back it up and then restore it to the new version. That was inconvenient."
"The breadth and depth of the solution's discovery of IT asset information means the system does most of the work, but they need to work on improving the database discovery part, especially for Oracle Exadata."
"Configuring rPDUs in the data center for Device42 required us to add multiple discovery jobs. The rPDUs were referred to the ISPDUs and daisy-chained. They would automatically assign a unique SMP port, but Device42 didn't allow SMP ranges, so we had to create a discovery job for each rPDU individually. We submitted a feature request to mitigate that."
"JSM's ability to handle large volumes of emails isn't great."
"If we can have an easier way to deploy this solution without the help of a consultant and a more reliable way of deploying procedures, it would be quite helpful."
"At times you will need add-ons or additional software, so built-in features would be helpful."
"With Jira, we were unable to implement time-based automation in its ticketing system. We would like a feature where we can define tickets based on severity, then tickets are automatically escalated to the next level after a set period of time if they go unanswered."
"A lot of users have said that they want a feature that was on the on-prem version of Jira and the vendor can't deliver. They're either unwilling or unable to give feature parity."
"The interface could always be updated and improved."
"The initial setup of JIRA Service Management can be complex for new users. There is a lot of configuration."
"There is no notification regarding language upgrades."
Device42 is ranked 6th in IT Asset Management with 25 reviews while JIRA Service Management is ranked 2nd in IT Service Management (ITSM) with 73 reviews. Device42 is rated 8.4, while JIRA Service Management is rated 8.2. The top reviewer of Device42 writes "Good reporting and discovery capabilities, and helpful for understanding device dependencies and asset management". On the other hand, the top reviewer of JIRA Service Management writes "Customizable, stable, and integrates well". Device42 is most compared with ServiceNow, ServiceNow CMDB, Infoblox IPAM, BMC Helix Discovery and NetBox.dev, whereas JIRA Service Management is most compared with ServiceNow, ManageEngine ServiceDesk Plus, Freshdesk, BMC Helix ITSM and OpenText Service Management Automation X (SMAX).
We monitor all IT Asset Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
