Jira Service Management vs. ManageEngine ServiceDesk Plus

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

ServiceDesk Plus is very easy to configure at the start, and then adjust the categories and rules as the implementation is refined. Its greatest strength is the ability to program without requiring a full time administrator. There is very little jargon involved. Reporting not so much. The canned reports are useful but do not always cover some of the basics. Fortunately, the user groups freely share report definitions so one could springboard from something close to your desired result.

Incentivized

• Manageable workflow to ensure all users follow the same process.
• Can ban boards for easy visual of ticket status.
• Very flexible tool that can adapt to lots of different uses outside of the traditional service desk model.
• Added communication tools help you get out of e-mail jail.

Incentivized

• Ticket logging for end users, so they can see the progress on their help requests
• Asset management; it has an agent that can be installed on machines which can then feed back information on installed software, active times, logged on user etc
• Project management; larger projects can be managed within ManageEngine ServiceDesk as well as end user help tickets, where progress/milestones etc can be recorded
• Active Directory import of users, so that it automatically updates when users are created/deleted and links their accounts in ManageEngine ServiceDesk with their email address as well to enable email alerts

Incentivized

• 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.

Incentivized

• When trying to select the top row ticket, you have to be careful not to select all tickets. Happened to us twice and we assigned all open tickets to one technician. Took a few minutes to correct.
• Site is sometimes a bit sluggish to respond. Don't know if that is an issue with our network infrastructure or the program itself, though.
• When users send emails to the help desk, we sometimes experience delays until the tickets appear on the site for the technicians.

Incentivized

we are looking at other tools like Zendesk which may replace ServiceDesk. We are currently evaluating both tools to see which one would serve our needs better

Incentivized

Jira Service Management tool will serve it's purpose to do what it is meant to be. It has it's own limitataions on few features, however it's the industry standard ticketing tool. All covers all the processes that required to resolve the issues. It has various use cases in incident management, Request management etc.

Incentivized

It is still very cumbersome, lots of data entry on the back end to build how we want it but it is still not completely user friendly. Many functions still dont work and contacting someone for help isnt always easy or we get told solutions for issues we have just arent built yet.

Incentivized

I gave JIRA a 9 rating since for me JIRA works according to its purpose. Since there is a customer portal, our clients can leave a comment or communicate with us using the PR ticket that way it is easier for us to also request any additional information we need for our investigation.

Our network administrator usually gets a good response when contacting ManageEngine ServiceDesk Plus customer service. They are quick to respond and so far have been able to eliminate most of our issues. We have been through several upgrades of the software over the years and have no issues to report in regards to customer service.

Incentivized

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.

Incentivized

Spiceworks was free, which obviously had both benefits and limitations - I will say that the community around Spiceworks has always been great. If we could replicate that experience with the ME user base, it would be terrific.

Incentivized

• JIRA has been incredibly useful. Our work is more organized and easier to view by the team members as well as upper-level people.
• Our work is correctly assigned and when there are issues, they can be immediately addressed within the tool.
• Users can attach screenshots or files of issues that help clarify the ticket. Developers can attach relevant data as well.

Incentivized

• The tool does not scale well from an ROI perspective. As you add a customer, you must add a new instance, hence a new license.
• The tool is probably on the expensive side (34,000 USD per 130 technicians per year).
• There is no usage beyond incident, change, and problem management. The CMDB feature is extremely limited and cannot generate additional ROI. There is no knowledge-base or integration with other software (other than ME Desktop Central).

Incentivized