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 (4th), IP Address Management (IPAM) Tools (5th), 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 5.9%, down 6.4% compared to last year.
JIRA Service Management, on the other hand, focuses on IT Service Management (ITSM), holds 9.5% mindshare, down 12.2% since last year.
IT Asset Management
IT Service Management (ITSM)
 

Featured Reviews

AHMEDKASSAB - PeerSpot reviewer
Allows us to determine the exact placement of assets based on the building maps and the room details
In my experience, I believe that the key concern is the pricing strategy of the solution. Instead, other solutions are much more cost-effective. Previously, Device42 has altered the pricing model to include a subscription fee which I see as very costly. They should change their pricing strategy and license scheme, conduct market research and ensure that they provide the right product in the market at the right price.
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 way the solution’s automatic IT asset discovery and inventory functionality works is you set up a discovery job, then you can schedule it to run. I schedule all of the runs daily at different times so nothing is interfering with anything else. It's nice to know that you can set up the scan, schedule it, and sit back. You can check them every day and make sure everything ran, making sure nothing had errors, then you're good to go. Anything new is going to automatically be discovered, which is nice. It takes some of the stress off because you don't have to know, "If this team opened new servers, we need make sure now it will automatically pick them up." It is one less thing to worry about. It gathers a lot of data points."
"The continuous asset discovery is good because it means not having to manually input all the small data, such as IP addresses, leases, etc. It helps and saves us a lot of time."
"The REST API abilities enables us to run scripts that pull information from our servers about software, storage, etc. Anything we need is pushed through REST API to the Device42 server and reflected in the report it generates."
"The asset inventory is great because previously we had devices all over the place. We have been able to do multiscans to find devices that we didn't know about, which was great."
"The import/export for bulk operations is a valuable and good feature."
"Device42 has everything in one place and links it altogether. This helps when you need to figure out where things are going wrong, where things are happening, or how everything is linked together."
"A big plus for Device42 was the auto-discovery. With it, we have updated devices, updated systems, and up-to-date systems."
"The solution's agentless approach to asset discovery is very important for us because installing agents on physical or virtual devices is not easy in our company. We have to escalate these kinds of things to different levels of security. Not having to install agents makes it easy for us."
"The query language and the ability to create views of the data are very useful."
"It is much more controlled and allows for different kinds of customization that we can plan and implement based on the project requirements."
"The platform is easy to use."
"Jira lets us customize the workflow to meet our requirements. The email and alert features are also handy."
"The dashboards in Jira have been the most useful feature."
"One of the valuable features is that an automatic response or action can be taken on tickets."
"We get software developed faster."
"We have an Agile environment and using Jira makes it easy to adhere to Agile best practices."
 

Cons

"Mapping items wasn't as intuitive as importing in Device42, so this is an area for improvement."
"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."
"If I want to delete an asset from a cabinet it does take a while. And if I'm doing it in bulk — say, for example, if we have one cabinet that has 20 servers in — if I want to remove all 20 servers, I have to do them individually, which is a bit time-consuming. If there were a way that I could just bulk-remove everything from there, that would definitely save some time."
"The dependency mapping can be quite slow sometimes, if you've got a lot of things connecting to services. It can be very slow to build up the map."
"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."
"Device42 is a main part of our processes. We need reliability, not only in terms of the data but with the solution itself. It's really difficult when we have 10 minutes of Device42 downtime because none of our teams can work for those 10 minutes, and it's more time lost if there is longer downtime. An improvement would be to have a cluster implementation of Device42 to have high-availability and ensure that we don't have downtime in case of failure."
"I would like to see API management as an additional feature in the tool's future versions. It will give more API security."
"It would be nice for the agent to have an installer versus a single file across multiple systems."
"Integration possibilities with other products that are not Atlassian would be helpful. Support should also provide separate installation guides for each product even though they are easy to install."
"The product could improve its asset management."
"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."
"It has change management and incident management, but CMDB is not there. It's also not as user-friendly as ServiceNow."
"The deployment can be a bit complex, especially for those who are not technical."
"The documentation needs improving, it's difficult to find specific procedures."
"At times you will need add-ons or additional software, so built-in features would be helpful."
"It would be beneficial if we could turn comments into subtasks or other JIRA tickets directly."
 

Pricing and Cost Advice

"It's in the top-three most expensive solutions in terms of cost, but it has all the features that are needed."
"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."
"The problem with using other vendor, like BMC, is the pricing. The price is so horrible and nobody wants to pay this money."
"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."
"The product cost is low. It is quite cheap."
"Our licensing costs are on a yearly basis."
"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."
"I price of JIRA Service Management is reasonable."
"The pricing is very competitive and I think that it is okay."
"For the people like us, the lower the price, the better. But when compared to other competitors, I think it's Jira's price is okay."
"It's not really expensive, especially when you compare to ServiceNow or other solutions, and it's not expensive to maintain."
"It costs around $150 to $200 per user."
"JSM's pricing is one of the best, starting at around $10 per user, per month, with volume discounts available."
"The price of the solution is becoming expensive and it should be reduced."
"I would suggest to always buy licenses through an Atlassian partner, so you can also rely on their expertise."
report
Use our free recommendation engine to learn which IT Asset Management solutions are best for your needs.
856,873 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
13%
Computer Software Company
12%
Manufacturing Company
9%
Healthcare Company
9%
Computer Software Company
19%
Financial Services Firm
11%
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.
856,873 professionals have used our research since 2012.