Try our new research platform with insights from 80,000+ expert users

Device42 vs JIRA Service Management comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Device42
Average Rating
8.4
Reviews Sentiment
7.2
Number of Reviews
25
Ranking in other categories
IT Asset Management (9th), Configuration Management Databases (3rd), IP Address Management (IPAM) Tools (4th), Data Center Infrastructure Management (6th)
JIRA Service Management
Average Rating
8.2
Reviews Sentiment
7.1
Number of Reviews
86
Ranking in other categories
Help Desk Software (2nd), IT Service Management (ITSM) (2nd)
 

Mindshare comparison

While both are Systems Management solutions, they serve different purposes. Device42 is designed for IT Asset Management and holds a mindshare of 6.2%, down 6.5% compared to last year.
JIRA Service Management, on the other hand, focuses on IT Service Management (ITSM), holds 10.9% mindshare, down 12.1% since last year.
IT Asset Management
IT Service Management (ITSM)
 

Featured Reviews

Krishna Gopal Singh - PeerSpot reviewer
Good reporting and discovery capabilities, and helpful for understanding device dependencies and asset management
Its price needs to be improved. It is more expensive than some of the other tools out there. Their support is good, but their knowledge base should be better. There should be a common area where we can search and find solutions for our queries or issues. We don't always need to raise a ticket with the Device42 support team. 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.
Karim Yousef - PeerSpot reviewer
Efficiently track and document projects with seamless tool integration
We are a management warehouse that provides services to different customers in different sectors. Primarily, we serve the banking sector and the military sector. We manage all the software delivery projects through tools such as JIRA Service Management or TFS Confluence is a great tool for…

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"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 reporting part is valuable. You have classic reports, and you can also do advanced reporting. They also have the DOQL feature for queries. You can write SQL queries to get your data and create custom reports."
"The IP address tracking [is valuable]... We have a lot of different devices and some of them have many IP addresses, so keeping track of which ones are assigned where is very critical for putting new devices on the network and giving them new addresses. All of our devices are statically assigned, so if we don't keep good records then we could accidentally assign a duplicate, which would cause problems on the network."
"A big plus for Device42 was the auto-discovery. With it, we have updated devices, updated systems, and up-to-date systems."
"The topology layout is the most valuable feature."
"One of the most valuable features in my experience is the precise tracking of hardware devices and their locations registered in the solution. The solution allows to determine the exact placement of assets based on the building maps and the room details. This feature has allowed us to gain upper hand on the customers and provide them with a great satisfaction because they can visually see the arrangement of their assets within the organisation or building."
"The most valuable feature was the ability to look up the different assets and see the different attributes that each one has, as well as being able to compare them to other assets."
"The pricing is reasonable."
"It makes the IT department more transparent and helps the employees."
"The tool's stability is very good."
"We can track, monitor, and get all the details we need from the end-user's point of view for any service request."
"I find the Kanban chart where we put each story in to be the most valuable feature. We use the Kanban chart to revise the project every morning in our five-minute meeting."
"JSM's best feature is the integration with other Jira products."
"Jira lets us customize the workflow to meet our requirements. The email and alert features are also handy."
"It's easy to set up the solution."
"Apart from ticket management and workflow, the Kanban board is one of the helpful tools in Jira."
 

Cons

"Mapping items wasn't as intuitive as importing in Device42, so this is an area for improvement."
"It was hard to know which assets I'd already looked at because if I looked up another asset with a similar name, they would still pop up. I would have to make sure I was looking at the right asset. The search function should be improved."
"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."
"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."
"While the automatic IT asset discovery is great, the first time using it can be confusing when you are configuring the SNMP. I don't remember for sure but I don't think it said "SNMP community," it said "password". The first time I used it I was thinking about communities but the tool said "password," and when you say "password" in SNMP you are thinking about SNMP version 3. This is the only thing that is confusing, although there were some devices that were not included in the discovery."
"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."
"Since I was focused on deploying connectors and getting all the servers to be scanned, one of the biggest pains was when a job would fail, then the output (logging) was poor. For example, "Why did it fail?" In these cases, you get a generic error. It doesn't point you in the right direction and tell you why you got the error, which is really annoying. There have been times I asked, "Is there somewhere I can see a better log as to why is this failing?" That would be a really nice improvement."
"I would like to see the user interface changed, it is not very user-friendly, and it transitions workflows."
"The solution should be more formalized. It could be more user-friendly."
"The way it handles subtasks can be improved. We would really like the ability to have different types of subtasks. If we have a user story for a feature, we would like to have a subtask for documentation, a subtask for requirements, a subtask for development, and a subtask for testing. Right now, we just make four subtasks, but there is no way to specify their type, so we have to add a custom field to specify what type of work is this. It just means you've got to look at more data. For logging time or time tracking, we would like to have something using which we can define the work type we're doing. We would like to log whether we're working on a bug, a new development, scope change, or rework. We've got a user story for which we do the dev, and then we have to do more dev. It is the same story, but some of it could have been a scope change, and some of it could be a rework because we either screwed up the first time or missed something obvious. Currently, we have to have a custom field and track that separately. It would be nice to have some kind of work type for logging time."
"The initial setup of JIRA Service Management can be complex for new users. There is a lot of configuration."
"JIRA Service could benefit from improvements to its voice support."
"Currently lacks an asset management module that can affect deployment."
"Include a split configuration in a layer part to allow cloud services to have almost full admin rights in SaaS."
"The main issue with this solution is there's no limited subscription available for plugins we only use for a few people. If we only have a team of twenty using a plugin, we still have to purchase a subscription for the whole 200 users."
 

Pricing and Cost Advice

"Our licensing costs are on a yearly basis."
"It's in the top-three most expensive solutions in terms of cost, but it has all the features that are needed."
"The problem with using other vendor, like BMC, is the pricing. The price is so horrible and nobody wants to pay this money."
"We pay $100,000 per year."
"Functionality-wise, Device42 is on par with industry standards, but price-wise, the solution is expensive. I'm rating the pricing for the solution as eight out of ten."
"The product cost is low. It is quite cheap."
"I am not involved in its pricing, but I have seen their plans during a discussion with the customer. For 500 servers, they were asking 50,000 USD. The cost of BMC Discovery was less than half. For the same thing, they were charging only 10,000 USD. Its pricing needs to be improved. As compared to other discovery tools, such as BMC Discovery and ServiceNow Discovery, its price is a little bit higher."
"On a yearly basis, our licensing is $10,000. However, our license is now nearly full with devices. We need the next bigger license with 5,000 devices, which will cost us $19,000. We pay for a set of licenses, a maximum number of devices, and a maximum number of IP addresses. We have the smallest amount of features, which is enough for us at this time."
"It costs around $150 to $200 per user."
"Right now, there are only two of us who are both agents on the help desk and developers. We might be on the free version because we're less than three agents or users. I'm looking at Zephyr tests, which have a $10 a month flat rate, so right now, it is $10 a month. There are lots of add-ons. They do a free version, a standard version, and a premium version. In the last company, we started on $50 a month. By the time I left, we were paying $4,500 a month. That was mainly because we had 100 users on Confluence. I bought an add-on for Jira software for which we had 10 users, and that was $5 per user per month. It was costing me $500 a month, whereas it should only be $50 a month. I don't know if licensing fee has changed. I'd like our whole company to use it, but the big problem is the licensing because the Confluence side is what is really useful, but if I add 30 users to Confluence and then buy an extension for Jira software, I've got to pay for 30 licenses, even though I've only got two users in Jira software. It is the one big disadvantage of cloud software. You always have to pay for the number of seats regardless of which product you are on. This will probably severely limit how many people would use it because I'm not going to start paying $10 per user per month for a Jira software add-on when there are only two people using it."
"I am using the free version, but my clients are paying for it. When they start, they evaluate it for 30 days, and after seeing the value, they move to its paid version."
"It is a cheaply priced product."
"This is pricey solution. Should we move to using all cloud solutions in our business, we may move to different tools that have multiple functionality versus having a solution for each area. This would be too pricey and we would need to replace Jira with a different solution that also offers other features."
"JIRA Service Desk has different pricing as it is based on agents. On average, the price is about $300 per agent."
"On a scale of one to five, where five is a good price and one is high, I would rate this solution as a three. It isn't cheap but it's not ridiculous."
"Costs are about $50 per user per year. JIRA is sold in user tiers of 25, 50, 100, 250, 500, 2000, 10,000, and unlimited users. It is bad when you have 51 users then the price is based on that 100 user tier. Users at 100 will be the most cost effective."
report
Use our free recommendation engine to learn which IT Asset Management solutions are best for your needs.
837,501 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Computer Software Company
13%
Manufacturing Company
9%
Government
7%
Computer Software Company
19%
Financial Services Firm
9%
Manufacturing Company
8%
Government
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What needs improvement with Device42?
The product must provide AI features. It would be very useful if I could create datasets or queries from an AI interface.
What is your primary use case for Device42?
I use the solution for physical assets management, IT management, and application dependency mapping.
 

Also Known As

No data available
JIRA Service Desk
 

Overview

 

Sample Customers

Computershare, Concur, Doosan, Fitch Ratings Inc., Fujitsu, HomeAway, Jasper Wireless, Mercedes-Benz, Square, Twitch, UCSB, Zayo Group Inc.
mgm technology partners, Telestream, Build.com, Zend Technologies, OfficeDrop, PGS Software, American Diabetes Association, NEPTUNE Canada
Find out what your peers are saying about ServiceNow, BMC, Qualys and others in IT Asset Management. Updated: January 2025.
837,501 professionals have used our research since 2012.