Jira Service Management (formerly Jira Service Desk, now including features from the former Mindville Insight, acquired by Atlassian in June 2020) is a service desk software that is purpose-built for IT, service, and support teams. The software provides everything IT and support teams need out-of-the-box for service request, incident, problem and change management. Jira Service Management integrates seamlessly with Jira Software so that IT and development teams can work better together. Users…
$0
per month
SolarWinds Web Help Desk (WHD)
Score 7.7 out of 10
N/A
SolarWinds
Web Help Desk is ticketing and IT asset management software. It is designed to
simplify help desk management. This solution includes built-in ticketing
management, asset management, change management, and knowledge base
capabilities.
Great to manage your issues in a clear and centralised way. If your development teams work with Jira, it will all naturally come together. Great way to manage the issues from end to end. - Very flexible if you have people who understands the set up and is able to configure it for your needs - Maybe not the best if you want something with very easy set up
SolarWinds WHD is well suited if you have a limited budget, as it costs less than many help desk software packages that are more full featured and modern in their design. It is not well suited to an environment where you want to manage inventory, users, purchases and tickets all in one package. It has an asset feature that we don't use but that looks quite limited. We track our assets and users separately from this.
Customized reporting allows us to track our service and support better, and find where we need improvements. This allows us to constantly upgrade our service levels and keep the customers happy.
Detailed tracking and response to the end users have led to quicker remediation of tickets. We are able to see where we need a better response or where to add additional resources for support.
Overall metrics allow us to staff properly for our tickets by location and remote users.
Ability to control the number of email notifications received (Note: this is a new feature in the Latest release but I personally haven not extensively looked at it and how well it solves the existing problem).
No way to reply to multiple tickets at once, say you got 4 tickets in for the same issue, there is no way you can reply to them in one stroke. Other Ticketing systems do have this ability.
Using a large number of add-ons to customize and add additional features adds up quickly and can become rather expensive.
Request forms are very basic and there is no native dynamic field ability available.
Because of AD integration, users sometimes try logging in with their email address and not AD credentials. The user then calls stating they can't put a ticket in, it would be nice if there was a method of matching the AD Email field with a login.
Setting up new techs with the building they are responsible for can be a little messy
We are definitely going to be sticking with Web Help Desk for the foreseeable future since the product is very inexpensive for the features that it provides, the integration that it has with our existing systems, and the ease for managing users, assets, locations, and tickets. Web Help Desk is a great product that is backed by even better support, which is well worth looking into if you are considering moving to a new ticketing system.
I gave JIRA a score of 9 since I am happy with the service it offers. I can easily see the SLA since it gives me visibility. I can pull up the reports I need. I can reach out to our clients using the PR ticket so it is hassle-free for me.
The system has time and time again proven to be much easier to use and setup for both technicians and end users. It is simple enough to enter a ticket for end users, and even easier to communicate with logging back and forth because you can reply to the ticket emails to enter comments on the tickets. The technician side is a little clunky at first, but after looking at it for a few minutes it's very clear to see what you need to do to accomplish the goals. The mobile interface is snappy and responsive. It's a great product overall.
I have not used the technical support from Atlassian. In terms of online help and resources, they are a bit limited thus making it more of a challenge to troubleshoot issues and learn more functionality. There aren't a lot of resources available on the Atlassian site besides developer documents. It would be nice to have a blog or forum where users can get the help they need.
SolarWinds is a great customizable and affordable ticketing system. We use SolarWinds Web Help Desk for IT and Software Development trouble ticket tracking and resolution. The reporting that SolarWinds provides is great since it helps us discover problem areas and fix those areas so they don't keep reoccurring
Take the time to roll out a test VM to configure and make changes to before doing a live deployment, this way you don't end up with a VM that has been tweaked and re-tweaked until it's perfect and instead end up with a final, polished product. I would also recommend taking the time to read through the support forums for figuring out minor issues that may pop up, chances are that you aren't going to be the first one to encounter them. When all is said and done, SolarWinds Support is VERY responsive and you shouldn't hesitate to contact them.
When I evaluated Spiceworks, it was not going to be replacing any ticketing systems. However, I did evaluate it and was not extremely impressed by the short demo I did. JIRA was selected because a branch of our company was already using it, so it made sense to consolidate into one service desk solution, and JIRA was the better option since it was less expensive and geared towards being a ticketing system.
Web Help Desk is definitely lacking in the UI/UX department compared to most other ticketing systems I have used int he past. It's very utilitarian; however, what it lacks in UI it makes up for in extensibility and customization. The main issue that the developers need to address is the use of a Web Objects back-end.
