We performed a comparison between JIRA Service Management and Spiceworks based on real PeerSpot user reviews.
Find out in this report how the two Help Desk Software solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The visibility features are great."
"There are two things that I value very much about this product. One is the service levels management – the SLA agreement management part of it – and knowledge management."
"One of the best features is that I can share tickets with team members, at which point any team member is able to pick one up and work on it."
"The most valuable features are the management tools."
"Jira Service Management has a workflow feature you can configure for your specific requirements. It also lets you efficiently manage service requests with team members."
"The most valuable features are the flexibility of defining your own workflows and automation around the workflows, and the integration with the gate or any repository."
"It's easy to set up the solution."
"Jira gets the basics right in terms of the product backlog and a scrum board teams can use to manage sprint backlogs."
"It lets us know whether devices are getting out of date and tracked warranties. Spiceworks also gave me visibility in terms of what software was installed on each device and its status."
"Spiceworks is generic and free."
"Tickets by e-mail, with actions by hastag."
"It shows the users that are currently logged in, which is not something that Active Directory by default will ever let you know up front."
"If you're in the market for a low-cost service desk system, Spiceworks is a good software solution to start out with, especially when it comes to startups and those organizations that don't currently have any existing service desk software in place."
"The solution is very stable. It's reliable and efficient."
"The nice thing about Spiceworks is always it's free. Monitoring of printers for low toner. Finding machines that have low memory or low hard disk space."
"The most valuable features are the inventory and personalization."
"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 product does not have the capability to sort queued tickets by product. This would be useful in making workflows more efficient."
"The interface could always be updated and improved."
"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 product could improve its asset management."
"In general, JIRA has no relation to customers or financials. Therefore, marketplace add-ons are needed to make it work for customer-facing systems."
"I don't think the program is very scalable."
"If JIRA were more of a substantial stand-alone product that covered more needs for project management, we wouldn't be using a suite of products."
"Having an integrated asset management tool, where I can plug in things that are offline, would be good."
"I would like the solution to allow for more direct interaction with computers. I can open tickets and I can see their status, but I can't interact directly with the computers themselves."
"The GUI must be improved."
"They've also tried to integrate it with social logins, like Twitter and LinkedIn, and that type of login authentication has no place in a corporate application."
"The network mapping could be improved. Putting together an actual bonafide network map would be really nice."
"Once a device was recognized on the network, Spiceworks never got rid of it even after you took it off the network. You had to go in and manually remove it."
"It would be nice to have remote access to the solution via a tablet. They also need remote control from a PC. Right now, to complete the technical support process, you have to have a tool to access the PC, and check the problems."
"With Spiceworks, like, when I open the websites, I have to Zoom in. I need to zoom in on those websites sometimes because it makes it horrible to use."
JIRA Service Management is ranked 2nd in Help Desk Software with 73 reviews while Spiceworks is ranked 16th in Help Desk Software with 47 reviews. JIRA Service Management is rated 8.2, while Spiceworks is rated 7.8. The top reviewer of JIRA Service Management writes "Customizable, stable, and integrates well". On the other hand, the top reviewer of Spiceworks writes "Good low-cost service desk system, but lacks in automation workflows and categorization ". JIRA Service Management is most compared with ServiceNow, ManageEngine ServiceDesk Plus, BMC Helix ITSM, Freshdesk and PagerDuty Operations Cloud, whereas Spiceworks is most compared with Zabbix, Lansweeper, ServiceNow and Freshdesk. See our JIRA Service Management vs. Spiceworks report.
See our list of best Help Desk Software vendors.
We monitor all Help Desk Software 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.